Skip to main content
Glama

Peru Data MCP by Vira

Peru trade with a country

peru_trade_by_country
Read-only

Peruvian companies trading with a given country, ranked by value.

`country_code` is the ISO 3166-1 alpha-2 code (US, CN, NL, ES, CL, JP, KR, DE, BR...). Returns each company's
exports to and imports from that country in USD. Use it to find who in Peru already sells to or buys from a market.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_code": "<country_code>"
    },
    "name": "peru_trade_by_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: results are companies ranked by value, and each carries both export and import figures in USD. It omits result limits, pagination, and whether companies with only one trade direction are included.

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 short sentences, each earning its place: purpose and ranking first, parameter format second, intended use last. No filler or restatement of the tool name.

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?

For a one-parameter, read-only lookup with no output schema, the description covers purpose, parameter encoding, and the shape of returned values. Missing are result-set size, sorting/pagination behavior, and whether both trade directions are always present — minor for this complexity level.

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

Parameters5/5

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

Schema coverage is 0% — the schema only says 'string' titled 'Country Code' — so the description carries the full burden and does so well, specifying ISO 3166-1 alpha-2 and supplying concrete example values (US, CN, NL, ES, CL, JP, KR, DE, BR). An agent can construct a valid call without further guessing.

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 opens with a specific verb+resource+scope: 'Peruvian companies trading with a given country, ranked by value,' and clarifies the shape of the result (exports/imports in USD). It does not explicitly distinguish itself from the similarly named sibling peru_company_trade, leaving some ambiguity for an agent choosing between them.

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

Usage Guidelines3/5

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

The closing sentence, 'Use it to find who in Peru already sells to or buys from a market,' gives a use case, which is more than nothing. However, it offers no exclusions, prerequisites, or named alternatives (e.g., when to prefer peru_trade_overview or peru_company_trade), so the agent must infer selection.

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