Peru Data MCP by Vira

Official PEN/USD exchange rate (SUNAT)

peru_exchange_rate

Today's official SUNAT exchange rate between the Peruvian sol (PEN) and the US dollar (USD), the rate used for tax and accounting purposes in Peru. Optionally converts amount from from_currency ("USD" or "PEN"). SUNAT convention: assets and sales use the buy rate, liabilities and purchases use the sell rate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "peru_exchange_rate"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	No
`from_currency`	No		USD

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full behavioral burden. It discloses freshness ('today's'), authority (SUNAT), and that conversion is optional/read-only, but says nothing about what happens on weekends or holidays when no rate is published, whether it falls back to the last published rate, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what the rate is before adding the conversion option and the buy/sell convention. Every sentence adds distinct information; nothing is redundant with the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of truth for a two-parameter tool. It covers the rate's identity and the conversion input, but leaves the return shape (single rate vs buy/sell pair, converted amount) and non-publishing-day behavior unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does: it defines the accepted values for `from_currency` ("USD" or "PEN") where the schema declares no enum, and clarifies that `amount` triggers conversion only when supplied (default 0 means rate-only). It does not say what currency the output rate is expressed in when a conversion is requested.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource type (today's official SUNAT PEN/USD exchange rate) with its domain purpose (tax and accounting in Peru) and an explicit optional conversion capability. No sibling in the listed catalog covers FX rates, so the tool is unambiguously identifiable from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real usage context: the rate is the one used for tax/accounting purposes, and it explains the SUNAT convention for choosing buy vs sell rate based on asset/sales vs liability/purchase context. It does not state exclusions or name alternatives, but there are no competing FX siblings to route away from.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Peru Data MCP by Vira tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?