Skip to main content
Glama

Peru Data MCP by Vira

Peruvian suppliers of a foreign buyer

peru_trade_buyer

Given a foreign buyer/consignee name (as returned by peru_trade_search_product), list the Peruvian companies that ship to it, with shipment counts, weight, ports used and date of the last shipment.

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": {
      "buyer_name": "<buyer_name>"
    },
    "name": "peru_trade_buyer"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyer_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discloses the return payload (counts, weight, ports, last shipment date), which is useful. But it is silent on match semantics (exact vs fuzzy buyer names), result limits or pagination, data freshness, and permission requirements for what is presumably a read-only lookup.

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?

A single dense sentence with no filler, front-loading the input contract before enumerating the outputs. Nothing is repeated and every clause adds information.

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 tool with no output schema, the description covers the input contract and the shape of the result, which is nearly everything an agent needs. The remaining gap is matching behavior and result-size expectations, which matter when a common buyer name could match many shippers.

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 coverage is 0%, so the description must define the lone parameter, and it does: buyer_name is a foreign buyer/consignee name, and should be the value returned by peru_trade_search_product. That provenance constraint is real meaning beyond the schema's bare 'Buyer Name' string. It stops short of specifying format or whether partial names are accepted.

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 verb (list) and resource (Peruvian companies shipping to a given foreign buyer), plus the exact returned fields (shipment counts, weight, ports, last shipment date). This is clearly distinguishable from siblings like peru_company_trade or peru_trade_by_country, which are oriented differently.

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?

Explicitly ties invocation to a prior call, naming peru_trade_search_product as the source of the buyer_name value, which gives a clear usage chain. It does not state when NOT to use it (e.g., looking up Peruvian exporters of a product) or what to do if the buyer name is ambiguous.

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