Skip to main content
Glama

Australia Tenders

by io.github.pipeworx-io
OverviewAdmin

Au Search Contracts

au_search_contracts
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax releases to return (1–500). Default 25. The API pages 100 at a time; higher limits follow the cursor.
date_toNoEnd of window, ISO-8601 (e.g. "2026-06-30"). Defaults to now.
date_fromNoStart of window, ISO-8601 (e.g. "2026-06-01" or "2026-06-01T00:00:00Z"). Defaults to ~30 days ago.
notice_typeNoWhich date the window filters on: "contractPublished" (default), "contractLastModified", "contractStart", or "contractEnd".

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: +[
+  {
+    "date_from": "2026-05-01",
+    "date_to": "2026-05-31",
+    "limit": 50,
+    "notice_type": "contractPublished"
+  },
+  {
+    "limit": 100
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnly/openWorld/idempotent hints. Description adds pagination behavior and default date range, but does not cover potential rate limits or authentication needs, which are minimal concerns given annotations.

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 front-loaded with key guidance, concise two sentences plus a list of return fields, no wasted words.

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?

Given 4 param tool with full schema descriptions and annotations, description covers return fields and defaults; missing output schema but description suffices for usage.

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?

All 4 parameters have schema descriptions (100% coverage). Description adds context on defaults and pagination behavior, providing added value beyond schema.

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 searches Australian federal government contracts/tenders via AusTender API, with specific examples and distinction from web search.

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?

Explicitly states 'PREFER OVER WEB SEARCH' and provides example queries, clearly indicating when to use this tool.

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
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