Skip to main content
Glama

Awardia

by app.awardia
OverviewDiscussionsAdmin

search_tenders

Read-only

Free during beta. Find OPEN public tenders (deadline still in the future) by keywords, country, region, CPV sector and value. EU-wide from TED; for Portugal also every national call for tender of any value (Diário da República). Returns title, buyer, country, region, CPV codes, estimated value, submission deadline, official link and tender documents link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25
regionNoPlace name: district or municipality (e.g. 'Lisboa', 'Sintra'). Matches the work location or the buyer's name; most precise for Portugal.
keywordsNoWhat you are looking for. English works across all countries (matched via the EU CPV vocabulary); adding the same words in the target country's language (e.g. 'school renovation escola requalificação') also matches tender titles and descriptions.
countriesNoISO 3166-1 alpha-2 country codes where the work is performed, e.g. ["PT","ES"]
max_valueNoMaximum estimated value
min_valueNoMinimum estimated value
cpv_prefixesNoCPV code prefixes; '45' = construction, '72' = IT services, '3021' = computers
deadline_afterNoISO date; default now

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds non-obvious behavior the annotations do not: the tool is free during beta, and its corpus is TED EU-wide plus all Portuguese national tenders of any value. It still omits pagination/ordering behavior and any rate or quota limits.

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?

Three tight sentences with zero filler: pricing note, scope and sources, then return fields. The most decision-relevant constraint (open tenders only) is front-loaded.

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 and clarifies source coverage, which is what an agent needs to judge relevance. It falls just short of complete by not describing result ordering or how limit interacts with the max-25 cap.

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 100%, so the schema already explains every parameter, including keyword language handling and CPV prefix examples. The description only restates the facet list (keywords, country, region, CPV sector, value) without adding syntax or format guidance, so the baseline 3 applies.

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?

States a specific verb and resource ('Find OPEN public tenders') plus the exact scope constraint (deadline still in the future) and the two data sources (TED EU-wide, Diário da República for Portugal). An agent can distinguish this from award_history or expiring_contracts without opening any schema.

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

Usage Guidelines4/5

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

The 'OPEN tenders (deadline still in the future)' framing gives clear context for when this tool applies versus historical or contract-expiry siblings, and the source coverage tells the agent what geography it can serve. However, it never names an alternative tool or states an explicit when-not condition.

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