Skip to main content
Glama

Get tender details

get_tender
Read-onlyIdempotent

Retrieve full details for a single open Canadian tender by reference or solicitation number from search results, including dates, buyer, criteria, contacts, attachments, and links.

Instructions

Get the full record for one open tender notice: description, dates, buyer and end users, selection criteria, trade agreements, commodity codes, contact, attachments and links. Look it up by the reference_number or solicitation_number returned by search_tenders. A solicitation number shared by several notices returns all of them.

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
idYesReference number or solicitation number, exactly as shown in search results.
langNoOutput language; "both" returns each text field in English and French.en
max_description_charsNoCut the description to this many characters. Raise it when description_truncated is true and you need the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description is not the sole burden here. It still adds genuinely useful behavior beyond them: the one-to-many case where a solicitation number shared by several notices returns all of them, plus the list of returned fields. It says nothing about a not-found response or any result cap, which keeps it off a 5.

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 sentences, no filler, and it front-loads the returned-record summary before the lookup mechanics and the multi-result caveat. The field enumeration is dense but each item maps to real output content, since there is no output schema.

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, the description correctly compensates by enumerating the returned fields, and it handles the tricky solicitation-number case. What is missing is minor: behavior when the id matches nothing, and whether truncation signals appear only as described in the max_description_chars parameter.

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 100%, so the baseline is 3 and the schema already documents lang and max_description_chars. The description earns above baseline by tying the id parameter to two specific accepted shapes and by explaining the semantic consequence of passing a solicitation number (multiple notices returned), which the schema does not convey.

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 gives a precise verb and resource ('Get the full record for one open tender notice') and immediately enumerates what the record contains, which distinguishes it from search_tenders as a detail-fetch rather than a list operation. An agent can tell from the text alone that this returns a single full record, not a result set.

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 states the entry condition explicitly: look up by the reference_number or solicitation_number 'returned by search_tenders', naming the sibling that produces valid inputs. It does not spell out a when-not case (e.g., use search_tenders first if you have no id), 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.