Skip to main content
Glama

AY Tenders

Get one tender

get_tender
Read-onlyIdempotent

One notice's page: title, buyer, country, stage and notice type, estimated value, published date, deadline, CPV, NAICS and PSC codes, place of performance where the notice states one, and the official notice. Counts as one row.

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": {
      "id": "<id>"
    },
    "name": "get_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id a search returned, such as ted-768295-2026, or the page address.

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?

The annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real value beyond them by enumerating the returned fields and the row-counting semantics, but it says nothing about what happens for an unknown or malformed id.

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 sentence with no filler, and the core idea (one notice's page) comes first, followed by the field inventory. The long comma-separated field dump is dense but each item earns its place as return-value documentation.

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, enumerating the returned fields is exactly what the description needs to do, and it does so thoroughly. For a one-parameter read, the only real omission is not-found or error behavior, which is a minor gap.

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?

Schema coverage is 100% and the single id parameter is fully documented there, including the ted-768295-2026 example and the alternative page-address form. The description adds no meaning about the id beyond what the schema provides, so the baseline of 3 applies.

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 phrase "One notice's page" combined with the enumerated fields makes it clear this fetches a single tender record by id, and the singular scope separates it from a list or search tool. It never names a verb like "fetch" outright, so the retrieval action must be inferred from the field list.

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?

Nothing states when to call this instead of search_open_tenders or expiring_contracts. The clause "Counts as one row" hints at counting contexts, and the required id implies a prior search, but neither is framed as usage 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