Skip to main content
Glama

Peru Data MCP by Vira

Find Peruvian exporters and foreign buyers of a product

peru_trade_search_product
Read-only

Find which Peruvian companies export a product and which foreign companies buy it.

`product` is a keyword, ideally in Spanish as written in customs declarations (e.g. "arandano" for blueberry,
"palta" for avocado, "uva" for grape, "cobre" for copper, "harina de pescado" for fishmeal, "cacao", "cafe").
Returns Peruvian exporters (with RUC and total exports) and foreign consignees (with shipment counts and weight).
Use it to source suppliers in Peru or to identify buyers and competitors in a product 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": {
      "product": "<product>"
    },
    "name": "peru_trade_search_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing what comes back (exporters with RUC and total exports; consignees with shipment counts and weight), which tells the agent what to expect from this read-only query. It does not mention result limits, empty-result behavior, or that it queries live customs data, keeping it short of a 5.

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 structure is well ordered — purpose first, then parameter guidance, then return contents, then use cases. There is mild overlap between the opening line about foreign buyers and the closing line about identifying buyers and competitors, but no sentence is wasted outright.

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 tool with no output schema, the description covers input semantics, return shape, and intended use, which is the bulk of what an agent needs. Minor gaps remain around result volume and whether an unmatched keyword returns an empty set.

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% for the single parameter, so the description carries the full burden and does so well: it says the value is a keyword, recommends Spanish as used in customs declarations, and gives six concrete examples including multi-word terms like "harina de pescado". An agent could construct a good call from this text alone.

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 first line states a specific verb and resource: find which Peruvian companies export a product and which foreign companies buy it. It clearly identifies the two-sided output (exporters and consignees), though it never explicitly contrasts itself with the closest sibling peru_trade_buyer, leaving that differentiation to inference.

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?

The closing sentence gives concrete use cases: sourcing suppliers in Peru, or identifying buyers and competitors in a product market. That is real when-to-use guidance, but there are no exclusions or named alternatives for when another trade tool would be a better fit.

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