Skip to main content
Glama

Peru Data MCP by Vira

Look up a Peruvian company by RUC

peru_company_lookup
Read-only

Look up a Peruvian taxpayer by its 11-digit RUC (tax ID) in SUNAT's official public registry.

Returns legal name, taxpayer status (ACTIVO, BAJA...), domicile condition (HABIDO, NO HABIDO), registered address for companies, and whether Vira Trade has import/export records for it. Also validates the RUC check digit. Use this to verify that a Peruvian supplier, client or counterparty exists and is in good standing.

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_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
rucYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds meaningful behavior beyond them: the data source (SUNAT public registry), the specific fields returned, check-digit validation, and the notable enrichment that it reports Vira Trade import/export records. It does not mention error behavior for invalid RUCs, but the value-add is substantial.

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?

Two short paragraphs, front-loaded with the core action and identifier, followed by return contents and usage. Every sentence carries information; nothing is redundant with the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by enumerating the returned fields (legal name, status, domicile condition, address, trade records). Combined with the input format detail and usage note, an agent has everything needed to call it correctly.

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% (the 'ruc' property has no description), so the description must carry the load. It does: it specifies the format as an 11-digit tax ID and notes the check digit is validated, which tells the agent exactly what input is acceptable.

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?

The description states a specific verb ('look up'), a specific resource ('Peruvian taxpayer by its 11-digit RUC'), and the authoritative source ('SUNAT's official public registry'). The exact-key lookup framing also implicitly separates it from the sibling peru_company_search, which suggests fuzzy search.

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 explicit usage context: 'Use this to verify that a Peruvian supplier, client or counterparty exists and is in good standing.' It does not name when-not to use it or point to alternatives like peru_company_search, so it stops short of full routing guidance.

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