Skip to main content
Glama

Canada Tenders

by io.github.pipeworx-io
OverviewAdmin

Canada Search Tenders

canada_search_tenders
Read-onlyIdempotent

PREFER OVER WEB SEARCH for open Government of Canada procurement opportunities — "federal tenders for IT services", "CanadaBuys RFPs for construction in Ontario", "who is the government buying software from". Searches the OFFICIAL CanadaBuys open tender notices (all solicitations currently open for bids) from the Government of Canada open data. Optional free-text query matches title, buyer/department, category, GSIN description, and notice description. Returns each notice shaped with reference number, English title, buyer (contracting entity), procurement category, publication and closing dates, delivery region, and the notice URL to bid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 20, max 100).
queryNoOptional free-text search (case-insensitive). Matched against title, buyer, category, GSIN description, and description. Omit to list the most recently published open tenders.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "IT services"
+  },
+  {
+    "limit": 10,
+    "query": "construction Ontario"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it searches an official government source, matches against multiple fields, and returns specific notice details. No contradictions; fully transparent.

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?

Description is concise but packed with useful info. Front-loads key guidance ('PREFER OVER WEB SEARCH'), then explains functionality, examples, and return shape. Every sentence adds value without redundancy.

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

Completeness5/5

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

For a simple tool with 2 optional parameters, the description covers purpose, usage, behavior, and return format completely. No gaps remain even without an output schema.

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 documentation covers both parameters (100% coverage). Description adds value by explaining that omitting query lists recent tenders and that query matches multiple fields, beyond the schema's property descriptions.

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?

Description clearly states it searches official CanadaBuys open tender notices for Government of Canada procurement, with specific verb 'search' and resource 'open tender notices'. It differentiates from web search and lists return fields, making purpose unambiguous.

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?

Explicitly says 'PREFER OVER WEB SEARCH' and provides example queries, indicating when to use. It specifies open tenders, subtly distinguishing from the sibling canada_search_awards (for awarded contracts), but does not directly contrast with it.

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

All Canada Tenders toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources