Skip to main content
Glama
Sign In

Australia Tenders

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Au Get Release

au_get_release
Read-onlyIdempotent

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "CN4240933",
      "date_to": "2026-05-31",
      "date_from": "2026-05-01",
      "notice_type": "contractPublished"
    },
    "name": "au_get_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe OCDS ocid (e.g. "prod-fcd1c039...") OR the Contract Notice id (e.g. "CN4240933").
date_toNoEnd of the window, ISO-8601. Defaults to now.
date_fromNoStart of the window the contract falls in, ISO-8601. Defaults to ~30 days ago.
notice_typeNoWhich date to search on: "contractPublished" (default), "contractLastModified", "contractStart", "contractEnd".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date_from": "2026-05-01",
+    "date_to": "2026-05-31",
+    "id": "CN4240933",
+    "notice_type": "contractPublished"
+  },
+  {
+    "id": "prod-fcd1c039-ae3d-4e1c-9f2a-1234567890ab"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses the exact shape of the returned release (ocid, contract id, buyer, supplier, etc.), which goes beyond the annotation hints (readOnly, idempotent). It also mentions the key constraint of needing a date window, adding valuable behavioral context.

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?

The description is concise: three sentences covering purpose, constraint, and output contents. It is front-loaded with the main action and the critical constraint, with no unnecessary words.

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 tool with 4 parameters, no output schema, and annotations present, the description covers the purpose, usage constraints, and return structure comprehensively. It does not miss any critical information needed for correct usage.

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% and each parameter is described in the schema. The description adds context for why date_from/date_to are needed (no per-id lookup), but does not provide additional technical details beyond the schema. Baseline of 3 is appropriate.

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?

The description clearly states the tool fetches a single Australian government contract by OCDS ocid or Contract Notice id, distinguishing it from the sibling au_search_contracts which likely handles searches. The verb 'fetch' and resource 'single contract' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains that due to AusTender lacking a per-id lookup endpoint, the user must supply a date window. This tells the agent when to use the tool and what prerequisite information is needed. It implicitly contrasts with a search tool by emphasizing the single-id retrieval.

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

All Australia Tenders toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources