Skip to main content
Glama

Peru Data MCP by Vira

Search Peruvian companies by name

peru_company_search
Read-only

Search Peruvian companies by legal name (or partial name) and get their RUC.

Returns companies with foreign-trade records first (with export/import totals in USD), then other matches from the
SUNAT registry. Use the RUC with peru_company_lookup or peru_company_trade.

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": {
      "query": "<query>"
    },
    "name": "peru_company_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the result ordering (foreign-trade companies first, then other SUNAT registry matches) and what the enriched records contain (export/import totals in USD). It does not mention result limits, pagination, or behavior when the query is very broad — a real gap for an open-world search.

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: purpose first, then ranking/return behavior, then the follow-up tool handoff. No filler, and the most decision-relevant information is front-loaded.

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 adequately covers what comes back (companies plus RUC and USD trade totals) and the ordering logic. It stops short of describing result-count caps or how to narrow an overly broad name query, which matters for an open-world search tool.

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% for the single 'query' parameter, so the description must carry the load — and it does, clarifying that the query is a legal name or a partial name, which is the key invocation detail. It does not specify minimum length, accent handling, or whether RUC strings also match.

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 and resource — search Peruvian companies by legal name or partial name — and names the artifact returned (the RUC). It also distinguishes itself from peru_company_lookup and peru_company_trade, which take a RUC rather than a name.

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 routes the agent: use this when you only have a name, then feed the returned RUC into peru_company_lookup or peru_company_trade. It gives clear context and the handoff alternative, though it never states the inverse exclusion (e.g., that you should skip this tool if you already hold a RUC).

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