Skip to main content
Glama

Get award details

get_award
Read-onlyIdempotent

Retrieve full Government of Canada award notice records by reference, solicitation, or contract number, including supplier, value, dates, procurement method, criteria, and contacts.

Instructions

Get the full record for an award notice: supplier, value, contract dates, procurement method, selection criteria, limited tendering reason, trade agreements, commodity codes, description and contact. Look it up by reference number, solicitation number or contract number. A solicitation that led to several awards, as supply arrangements do, returns the 20 most recent and the total count.

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_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReference, solicitation or contract number, exactly as shown in search results.
langNoOutput language.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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavioral information beyond them: that a solicitation with multiple awards returns the 20 most recent plus a total count, which tells the agent how to interpret a list-shaped response. It doesn't cover not-found behavior or error cases.

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 sentences, front-loaded with the return content, then lookup keys, then the edge-case behavior. The long field enumeration is dense but each item is informative; no filler sentences.

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?

There is no output schema, so the description carries the burden of describing the return payload, and it does so with a field list plus the 20-award cap and total count. Remaining gaps are minor: no guidance on what happens for an unknown identifier or on whether the 20-award cap is configurable.

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%, so the schema already explains id, lang and max_description_chars, including the truncation workflow via description_truncated. The description restates the accepted identifier types but adds no format, syntax or validation detail beyond the schema, so baseline 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 description opens with a specific verb and resource ('Get the full record for an award notice') and enumerates the fields returned (supplier, value, contract dates, selection criteria, etc.), so the tool's scope is unambiguous. The contrast with search tools is only implied by 'full record' and 'exactly as shown in search results'; no sibling is named, which keeps it at 4 rather than 5.

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 lookup keys (reference, solicitation or contract number) and gives a concrete usage condition for the multi-award case ('A solicitation that led to several awards, as supply arrangements do'). It stops short of naming search_awards as the alternative for discovery queries or saying when not to use this tool.

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