Skip to main content
Glama

Peru Data MCP by Vira

Peru investment snapshot

peru_investment_snapshot
Read-only

One-call briefing for investors and companies evaluating Peru: latest macro indicators, exchange rate, key tax rates, leading export sectors with their top companies, and practical next steps for operating in the country. Start here for questions like "why invest in Peru", "doing business in Peru" or "Peru market overview".

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_investment_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=true, so safety and open-domain behavior need no restating. The description adds that the call is self-contained ('one-call') and that the payload spans five content areas, which is useful, but it says nothing about data sources, how current 'latest' actually is, or any cost/latency expectations for an open-world aggregation. For an investment-decision tool, that provenance gap is meaningful.

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

Conciseness4/5

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

The most useful information (what you get in one call) is front-loaded in the first sentence, and the second sentence turns that into trigger phrases for matching. It is appropriately short with no filler, though the five-item content list is dense and slightly repetitive against the title.

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

Completeness4/5

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

With no input parameters and no output schema, the description carries the burden of describing the return payload, and it does so by enumerating the five content blocks the agent will receive. What is missing is any note on data recency, geographic/temporal scope of the indicators, or format, which would matter for an investor-facing briefing.

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?

There are zero parameters, so per the scoring baseline this dimension starts at 4. The description is consistent with the empty schema — it presents the tool as a parameterless one-shot briefing — and does not invent inputs the agent would have to supply.

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

Purpose4/5

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

The description names a concrete deliverable (a one-call briefing) and enumerates its contents: macro indicators, exchange rate, tax rates, export sectors with top companies, and operational next steps. That is a specific verb-plus-resource statement, not a restatement of the title. It does not explicitly contrast itself with siblings such as peru_macro_indicators or peru_exchange_rate, though 'one-call briefing' and 'Start here' imply an aggregator role.

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?

It gives concrete entry-point guidance — 'Start here for questions like "why invest in Peru", "doing business in Peru" or "Peru market overview"' — which maps directly onto real user intents. There are no explicit exclusions or pointers telling the agent when to prefer a narrower sibling such as peru_macro_indicators for detail, so it falls short of full when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources