Skip to main content
Glama

defense-gateway

match_peruvian_procurement

Radar y clasificador de requerimientos técnicos y convocatorias SEACE/OSCE de software, IA y digitalización en el Estado peruano con códigos CUBSO sugeridos.

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": {
      "requirement_text": "<requirement_text>"
    },
    "name": "match_peruvian_procurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
requirement_textYesTexto del requerimiento, TDR o título de licitación en Perú

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely does not meet it. It hints that CUBSO codes are 'sugeridos' (suggested, not authoritative), which is useful, but says nothing about whether an external SEACE/OSCE source is queried, latency, rate limits, permissions, or how confident or complete the classification is.

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?

It is a single dense sentence with no filler, and the domain qualifier and output artifact are packed efficiently. It is a noun phrase rather than a front-loaded action statement, which slightly weakens scannability but wastes no words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool operates in a specialized domain (Peruvian procurement, CUBSO code taxonomy) with no annotations and no output schema, so the description must explain what comes back. It mentions only 'códigos CUBSO sugeridos' and omits the response shape, whether matching scores or ranked candidates are returned, and whether the result is a classification or a lookup against real tender data.

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

Parameters3/5

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

With one parameter and 100% schema description coverage, the schema already explains that requirement_text is the requirement text, TDR, or tender title. The description adds only the domain framing (Peruvian public sector procurement) and no additional detail on length, language, or formatting expectations, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific domain (SEACE/OSCE software, AI and digitalization requirements in the Peruvian State) and an output (suggested CUBSO codes), but its head terms 'Radar y clasificador' are nominal and ambiguous. It is unclear whether the tool searches a corpus of tenders, classifies a supplied text, or monitors a feed, so an agent cannot confidently predict the action from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this tool versus anything else, no prerequisites, and no stated exclusions or edge cases. The agent must infer usage entirely from the domain vocabulary.

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.