Skip to main content
Glama

Peru Data MCP by Vira

Imports and exports of a Peruvian company

peru_company_trade
Read-only

Real import and export activity of one Peruvian company, from official SUNAT/Aduanet customs declarations.

Returns totals in USD (FOB exports, CIF imports), yearly breakdown, top destination and origin countries, customs offices used and a sample of exported products. If the company is not loaded yet, it is fetched on demand (may take a few seconds). Use it for supplier due diligence, competitor analysis or sizing a Peruvian exporter.

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": {
      "ruc": "<ruc>"
    },
    "name": "peru_company_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
rucYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds meaningful context beyond them: the output contents (USD FOB exports, CIF imports, yearly breakdown, top countries, customs offices, product sample) and the on-demand fetch with a 'may take a few seconds' latency warning. It does not mention caching behavior or data freshness beyond the initial fetch.

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?

The source and scope lead, the return payload follows, and the operational caveat (on-demand fetch latency) plus use cases close it out. Every sentence carries information and there is no filler.

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 output schema, the description properly compensates by enumerating what is returned. The single remaining gap is the unexplained ruc parameter, which is the only thing an agent needs in order to call the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter 'ruc' is never explained in the description. Nothing states that ruc is the Peruvian tax identification number or what format/length is expected, so an agent gets no help beyond the bare property name.

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 states a specific resource and scope: 'Real import and export activity of one Peruvian company, from official SUNAT/Aduanet customs declarations.' The 'one company' scoping implicitly separates it from aggregate siblings like peru_trade_by_country or peru_trade_overview, but it never names an alternative to route against explicitly.

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 usage contexts ('supplier due diligence, competitor analysis or sizing a Peruvian exporter'), which is clear when-to-use guidance. It stops short of when-not-to-use conditions or naming the sibling tools that answer country- or product-level questions instead.

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