Skip to main content
Glama

AY Tenders

Contracts ending soon

expiring_contracts
Read-onlyIdempotent

Contracts in our seven sectors whose period ends in the coming months (3 unless you say, 12 at most), from UK award notices, Irish award dates plus the stated duration (an estimate, marked so) and USAspending. A contract ending is often re-tendered, but not always. Up to 10 rows an answer and 3 pages; 300 rows a day per address.

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": "expiring_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoWords in the title or the buyer's name.
regionNouk, ie (Ireland) or us. Leave it out for all three.
sectorNoit_services = IT systems & software, cybersecurity = Cybersecurity, medical_devices = Medical devices & pharmaceuticals, civil_works = Civil works & construction, energy_solar = Energy, solar & efficiency, cleaning_environment = Cleaning, environment & waste, events_marketing = Events, exhibitions & marketing.
months_aheadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: data provenance per region, the fact that Irish expiries are a duration-based estimate and explicitly marked as such, plus rate limits (300 rows/day per address). It does not describe the returned fields, which matters since no output schema exists.

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?

The definition is a single dense, front-loaded paragraph: resource and scope first, then sources, caveat, then operational limits. Every clause carries information, though the run-on parenthetical about Irish estimates is slightly awkward to parse.

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 a five-parameter read tool with no output schema, the description covers defaults, hard caps, rate limits, source coverage and the estimate caveat. The main residual gap is what a row actually contains, which the agent must discover by calling.

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?

At 60% schema coverage, the description supplies the missing meaning for months_ahead (defaults to 3, capped at 12) and the pagination model (10 rows per answer, 3 pages max). The query, region and sector semantics are left to the schema, which documents them adequately.

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 states a specific resource (contracts whose period ends) with explicit scope (seven named sectors, UK/Irish/USA sources), which an agent can readily distinguish from the open-tender siblings. It stops short of naming search_open_tenders or get_tender as the alternative, leaving that differentiation implicit.

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

Usage Guidelines3/5

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

The context of use is implied rather than stated: it explains that an ending contract is often re-tendered 'but not always', which hints at when this tool is the right entry point. There is no explicit when-to-use/when-not statement or named alternative for finding currently open opportunities.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources