Skip to main content
Glama

Search open federal tenders

search_tenders
Read-onlyIdempotent

Search open Government of Canada tender notices from CanadaBuys to find bidding opportunities by keyword, buyer, category, region, commodity code or closing date.

Instructions

Search currently open Government of Canada tender notices from CanadaBuys (requests for proposal, standing offer and supply arrangement requests, requests for information, advance contract award notices). Use it to find bidding opportunities by keyword, buyer, category, commodity code, delivery region or closing date. Returns short summaries; call get_tender for full details. With no arguments it lists the tenders closing soonest. Covers federal organizations only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language.en
sortNoDefaults to relevance when a query is given, otherwise closing_soonest.
buyerNoWords from the contracting or end-user organization name, in either language, e.g. "National Defence".
limitNoResults per page (1-50).
matchNoWhether a notice must contain all query terms or any of them. An explicit OR in the query always applies.all
queryNoKeywords searched in titles, descriptions, commodity names and buyer names. Words match in English and French, ignoring case and accents. Use "double quotes" for an exact phrase, a trailing * for a prefix (engineer*), and uppercase OR between alternatives.
offsetNoResults to skip, for paging.
regionNoText contained in a region of delivery, e.g. "Ontario", "National Capital Region", "British Columbia". Nationwide tenders are listed under "Canada" and are not returned for a provincial filter.
unspscNoUNSPSC commodity code or prefix. A segment or family code such as 43000000 or 4323 also matches every code beneath it.
categoryNoProcurement categories; a notice matching any listed category is returned.
notice_typeNoText contained in the notice type, e.g. "Request for Proposal", "Request for Information", "Standing Offer".
closing_afterNoOnly tenders closing on or after this date (YYYY-MM-DD).
closing_beforeNoOnly tenders closing on or before this date (YYYY-MM-DD).
published_afterNoOnly tenders published on or after this date (YYYY-MM-DD).
include_past_deadlineNoThe source lists some notices as open after their closing date has passed. They are hidden unless this is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that results are short summaries requiring a get_tender follow-up and that a no-argument call lists soonest-closing tenders. It does not add pagination/limit behavior or volume expectations beyond what the schema states.

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?

Four short sentences, front-loaded with the resource and scope, then coverage, then usage, then the sibling hand-off and the federal-only caveat. No sentence is filler and the ordering prioritizes what an agent needs to decide to call it.

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?

For a 15-parameter read-only search with no output schema, the description covers scope, return shape (short summaries), the escalation path to get_tender, and default behavior. Missing only minor operational detail such as result caps per page, which the schema already conveys via the limit parameter.

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 description coverage is 100%, so every one of the 15 parameters is already documented with enums, defaults, formats and examples; that sets the baseline at 3. The description only implicitly explains the no-argument default sort, adding essentially nothing beyond the schema's own default note.

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?

States a specific verb and resource ("Search currently open Government of Canada tender notices from CanadaBuys") and enumerates the notice types covered in parentheses. It also distinguishes its output from the sibling get_tender ("Returns short summaries; call get_tender for full details"), so an agent can tell the two apart without opening schemas.

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?

Gives concrete when-to-use framing ("Use it to find bidding opportunities by keyword, buyer, category, commodity code, delivery region or closing date") and an explicit scope limit ("Covers federal organizations only"). It stops short of naming when to prefer siblings such as search_standing_offers or search_awards, and its mention of standing offer notices could overlap conceptually with the dedicated standing-offer tool.

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