Skip to main content
Glama

tenderkit

procedure_results

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 observed

TDQS

B3.2/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 does add real value: it states that the latest formal award per lot is returned and that cancelled lots come back with status CANCELLED and no contractor. It says nothing about read-only nature, error behavior for invalid source/number, or result volume, so the disclosure is useful but partial.

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 and then the return shape; no filler. The only inefficiency is that the most useful detail (award/cancellation semantics) is separated from the identifier discussion, which is absent.

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

Completeness3/5

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

An output schema exists, yet the description still helpfully summarizes return semantics, and it covers the cancelled-lot edge case. However, for a tool whose two required parameters are entirely undocumented at 0% schema coverage, the definition leaves the agent guessing how to construct a valid call.

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 description does not compensate: it never explains what 'source' means (source system/registry?) or the format of 'number'. The only hint is the loose reference to 'procedure_id', which does not map cleanly onto either parameter 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 opens with a specific verb and resource: 'Show one procedure's contract and result notices linked by procedure_id.' That clearly distinguishes a single-procedure lookup from the search_* siblings. It is slightly muddied by naming 'procedure_id' as the link key while the schema's required inputs are 'source' and 'number'.

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 implied rather than stated: 'one procedure' signals a single-record fetch as opposed to the search tools, but there is no explicit when-to-use/when-not guidance or named alternative. Nothing tells the agent what to do if it has a notice but not a procedure number.

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.