MCP tool: loyalty_tiers

2 min read

loyalty_tiersMCP tool

tools/callJSON-RPC method

Read-onlyPublic data

Tool

Name	`loyalty_tiers`
Transport	JSON-RPC 2.0 via POST /public/v1/mcp (`tools/call`)
Auth	None (public ring)

What it does

Returns the Credicorp loyalty ladder — the tiers, their thresholds and headline benefits — the same vocabulary the public loyalty endpoint publishes, so an agent can explain the rewards accurately.

Input

No arguments.

Output

The tier ladder with each tier's name, threshold, headline benefit and any cooldown — reconciling with GET /public/v1/loyalty/tiers. It carries vocabulary and figures only, no customer data.

How agents use it

A lending assistant typically calls loyalty_tiers when a prospect asks what they get for staying, or to explain the rewards ladder alongside a quote. Because the data reconciles with the public loyalty endpoint and carries no customer data, the agent can present thresholds and benefits confidently without any authentication. Pair it with eligibility_criteria and how_to_apply to give a complete, accurate picture before handing the user to apply.

Frequently asked questions

Does loyalty_tiers reveal a customer's own tier?

No. It returns the public ladder vocabulary — tiers, thresholds, benefits — with no customer data. A customer's own tier lives behind authentication in the portal.

Is this the same data as the loyalty endpoint?

Yes. It reconciles with GET /public/v1/loyalty/tiers because both read the single-sourced tier config, so the agent and the website tell the same story.

Should I cache the loyalty_tiers result?

Yes. It is config vocabulary with no per-customer data, so caching it briefly is safe and reduces calls. Refresh periodically so a change to the ladder reaches your agent without a restart.