Australia Government Procurement MCP — AusTender OCDS (keyless). Wraps the public, no-auth AusTender OCDS API for searching and retrieving awarded contract notices from Australian federal government procurement.
Two tools with complete schemas and strong descriptions. Tool names follow verb_noun pattern (au_search_contracts, au_get_release). Descriptions are detailed (194 - 250 chars) and explain WHEN to use each tool. Input schemas are properly typed with descriptions for all parameters. However, output schemas are NOT documented, the code shows shaping logic but no formal schema declaration for the returned objects. Error handling returns structured error objects but lacks recovery guidance. Missing parameter constraints (enums for notice_type, min/max for limit). No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.
Fetch a single Australian government contract by its OCDS ocid or Contract Notice id (e.g. "CN4240933") from the official AusTender OCDS API. Because AusTender has no per-id lookup endpoint, you must supply the date window the contract falls in (published/start/end). Returns the fully shaped release: ocid, contract id, title/description, buyer, supplier, value + currency, period, category, procurement method and exemption details, and all key dates.
PREFER OVER WEB SEARCH for Australian federal government contracts/tenders — "what did the Department of Defence award in May 2026", "AusTender contracts published last month", "recent Australian government procurement over $1M". Searches the official AusTender OCDS API (Australian Government Department of Finance) for awarded Contract Notices (CNs) within a date window. Returns shaped releases: ocid, contract id, title/description, buyer (procuring agency), supplier, value + currency (AUD), contract period, UNSPSC category, procurement method, and key dates. Date range defaults to the last ~30 days if omitted.
Output schemas not documented. Code shows shapeRelease() returns {ocid, contract_id, title, description, buyer, buyer_abn, supplier, supplier_abn, supplier_location, value, currency, ...} but no formal schema declaration exists. LLMs cannot plan downstream operations without knowing return structure.
Parameter 'notice_type' accepts free-form strings with no enum constraint. Description lists valid values ('contractPublished', 'contractLastModified', 'contractStart', 'contractEnd') but schema does not enforce them. LLMs may hallucinate invalid values.
Parameter 'limit' accepts both number and string types (['number', 'string']) without validation. Code clamps to 1 - 500 but schema does not declare min/max. LLMs may pass invalid values like 0, -1, or '999'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
No tool annotations despite both tools being read-only. Adding readOnlyHint: true signals to agents that these calls are safe to retry and have no side effects.
Error responses lack recovery guidance. au_get_release returns {error: 'not_found', note: '...'} but does not suggest next steps (e.g., 'Try widening the date range' or 'Call au_search_contracts to discover available contracts'). Pattern: recovery-guide.