Skip to main content
Glama

procedure_results

Retrieve contract and result notices for a procurement procedure by source and number, returning the latest award per lot with contractor, price, bid count, date, status, and cancelled lots.

Instructions

Show one procedure's contract and result notices linked by procedure_id.

    Returns the latest formal award per lot (contractor, price, bid count, date, status).
    Cancelled lots appear with status CANCELLED and no contractor.
    

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": {
      "source": "<source>",
      "number": "<number>"
    },
    "name": "procedure_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful result semantics: the latest formal award per lot with its fields, plus the edge case that cancelled lots appear with status CANCELLED and no contractor. It does not state read-only behavior explicitly, nor what happens when the procedure is unknown or has no awards, so the safety and failure profile is incomplete.

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?

Three short sentences, front-loaded with the core purpose before the return-shape detail. No filler or repetition; only the stray indentation and the dangling procedure_id reference cost it a point.

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?

An output schema exists, so the return-value sentences are somewhat redundant, while the genuinely undocumented area — the two required parameters at 0% schema coverage — is left unaddressed and confused by the procedure_id reference. For a tool whose only inputs are unexplained, this leaves a material gap in an otherwise well-specified result contract.

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%, so the description must explain the two required parameters, and it does not — neither 'source' (which source system?) nor 'number' (procedure number format?) is defined. Worse, the description anchors on 'procedure_id', a key that does not exist in the schema, which can actively mislead the agent about what to pass.

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?

States a specific verb ('Show') and a well-scoped resource ('one procedure's contract and result notices'), making clear this is a single-procedure lookup rather than a search. It does not explicitly contrast itself with the sibling search_results, so the agent must infer the distinction from the word 'one'.

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

Usage Guidelines3/5

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

Usage is only implied: 'one procedure's' suggests this is the lookup path once a procedure is known, versus a search tool. There is no explicit when-to-use or when-not-to-use statement and no named alternative, leaving the routing decision partly to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.