Skip to main content
Glama

Search standing offers and supply arrangements

search_standing_offers
Read-onlyIdempotent

Search active federal standing offers and supply arrangements to find pre-qualified suppliers, check what a supplier holds, and see when agreements expire or may be re-competed.

Instructions

Search active federal standing offers and supply arrangements issued by Public Services and Procurement Canada: pre-qualified suppliers that departments can buy from without a new open competition. Use it to see who already holds an agreement for a commodity, what a given supplier holds, or when agreements expire and may be re-competed. Agreement types: SA (supply arrangement), NMSO and RMSO (national and regional master standing offers), NISO, RISO and DISO (national, regional and departmental individual standing offers).

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

Input Schema

NameRequiredDescriptionDefault
langNoOutput language.en
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 agreement titles, commodity names, supplier names and departments. 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 delivery point, e.g. "Alberta" or "National Capital Region".
supplierNoWords from the supplier legal, operating or standardized name.
commodityNoUNSPSC commodity code or prefix; a segment or family code also matches every code beneath it.
departmentNoWords from the department the agreement serves, in either language.
agreement_typeNoAgreement type code, e.g. SA, NMSO, RMSO, NISO, RISO, DISO.
include_expiredNoAlso return agreements whose expiry date has passed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/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 real context beyond that — the issuing authority, the fact that only active agreements are returned by default, and what the agreement-type codes mean — but says nothing about result volume, paging behavior, or the 50-per-page / 100k offset ceilings the agent will hit.

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?

Two sentences, front-loaded with the resource and its scope, then a compact glossary of agreement codes. The code list is long but maps directly to a queryable parameter, so it earns its space; no filler or restated title.

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 an 11-parameter, all-optional read-only search with no output schema, the description covers what the corpus is and what questions it answers. It does not sketch the shape of a result record (supplier, commodity, expiry, region) or default ordering, which would have helped an agent page and interpret results without an output schema.

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 every one of the 11 parameters is already documented, which sets the baseline at 3. The description only genuinely adds meaning for agreement_type by expanding the bare codes into SA / NMSO / RMSO / NISO / RISO / DISO full forms; the rest (supplier, commodity, expiry) is already framed in the schema itself.

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 gives a specific verb and resource ('Search active federal standing offers and supply arrangements issued by Public Services and Procurement Canada') and defines the concept in procurement terms ('pre-qualified suppliers that departments can buy from without a new open competition'). That domain framing implicitly separates it from awards/tenders, but it never names search_awards or search_tenders as the alternatives an agent should consider.

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?

Three concrete usage contexts are spelled out: seeing who already holds an agreement for a commodity, what a given supplier holds, and when agreements expire and may be re-competed. There are no explicit exclusions or 'use X instead when...' routing, so an agent still has to infer the boundary against the award and tender search siblings.

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