Skip to main content
Glama

Awardia

by app.awardia
OverviewDiscussionsAdmin

expiring_contracts

Read-only

Free during beta. Public contracts whose term ends soon, so the buyer will likely re-tender: a sales pipeline before tenders are published. Returns buyer, incumbent supplier(s), value, start and expected end date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyerNoPart of the buyer's name
limitNo
regionNoPlace name: district or municipality (e.g. 'Lisboa', 'Sintra'). Matches the work location or the buyer's name; most precise for Portugal.
countriesNoISO 3166-1 alpha-2 country codes where the work is performed, e.g. ["PT","ES"]
min_valueNoMinimum awarded value
cpv_prefixesNoCPV code prefixes; '45' = construction, '72' = IT services, '3021' = computers
months_aheadNoLook-ahead window, default 12 months

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Place name: district or municipality (e.g. 'Lisboa', 'Sintra'). Matches the work location or the buyer's name; most precise for Portugal.",
+  "maxLength": 100,
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint=false). The description adds meaningful context beyond that: the 'free during beta' cost signal, the inference logic (term ending soon implies likely re-tender), and the returned fields, which is useful since there is no output schema.

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?

Three tight sentences; the cost note is front-loaded and each sentence carries weight (purpose, framing, return contents). No filler or redundancy.

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?

With no output schema, the description usefully enumerates the returned fields (buyer, incumbent suppliers, value, dates), and high schema coverage plus zero required params means little else is needed. Pagination/limit behavior is not addressed, a minor gap.

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 description coverage is 86%, so the schema already documents essentially all parameters (region, months_ahead, cpv_prefixes, etc.) in detail. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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?

States a specific resource (public contracts whose term ends soon) and explains the purpose concretely as a pre-tender sales pipeline. It conceptually distinguishes itself from search_tenders by being 'before tenders are published', but never names a sibling, so differentiation relies on inference.

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 framing as 'a sales pipeline before tenders are published' implies when an agent should reach for it, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. search_tenders or award_history). Usage is only implied.

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

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