Skip to main content
Glama

Spain Tenders

by io.github.pipeworx-io

Es Tender By Status

es_tender_by_status
Read-onlyIdempotent

List SPANISH government tenders filtered by lifecycle status on PLACSP (Spain public procurement / licitaciones, contrataciondelestado.es official feed): PUB = published and open for bids, PRE = prior information notice (anuncio previo), EV = under evaluation, ADJ = awarded (adjudicada), RES = resolved / award finalized, ANUL = cancelled. Ideal for "currently open Spanish tenders" (status PUB) or "recently awarded Spanish government contracts" (ADJ or RES). Returns compact shaped notices with title, contracting body, EUR budget amounts, CPV codes, contract type, procedure, submission deadline, and notice URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax notices to return (default 20, max 100).
statusYesStatus code: PUB | PRE | EV | ADJ | RES | ANUL.

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: +[
+  {
+    "limit": 15,
+    "status": "PUB"
+  },
+  {
+    "limit": 10,
+    "status": "ADJ"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds value by disclosing the data source (PLACSP, contrataciondelestado.es) and the return structure (compact notices with title, contracting body, budget, etc.). This is useful behavioral context beyond the annotations, though it doesn't mention pagination or error behavior.

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 appropriately sized for the tool's complexity. It packs essential information into two sentences: what the tool does, the meaning of each status, ideal use cases, and return fields. Every clause adds value, and the structure is logical (action, status codes, use cases, output). No redundancy or filler.

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 no output schema, the description compensates by listing the return fields. It also covers the full status vocabulary and gives usage context. The tool is a simple filtered list, and the description covers its essential behavior. Minor gaps like pagination limits are already in the schema, and error handling is not critical for this read-only tool.

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?

The input schema provides descriptions for both parameters (status and limit), so baseline is 3. The description adds significant meaning by explaining each status code in detail (e.g., 'PUB = published and open for bids', 'ADJ = awarded'). This goes beyond the schema's simple enumeration, helping the agent select correct values. The limit parameter is already well-defined in the schema, so no extra info is needed there.

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 states a clear and specific action: 'List SPANISH government tenders filtered by lifecycle status on PLACSP'. It distinguishes itself from sibling tools like es_tender_recent and es_tender_search by focusing on status filtering with detailed status code semantics. The verb 'List' and the resource 'Spanish government tenders' are explicit, making the tool's purpose unambiguous.

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 description provides concrete usage guidance: 'Ideal for "currently open Spanish tenders" (status PUB) or "recently awarded Spanish government contracts" (ADJ or RES)'. This tells the agent when to use the tool. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of full guideline coverage.

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

All Spain 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.

TDQS

A3.7/5.0
Disambiguation2/5

Several clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (the beta currently matches stable exactly), and the Polymarket tools all circle around edge/arbitrage detection with fuzzy boundaries. The Spain tender tools and utility tools are distinct, but the overlapping clusters are enough to cause misselection.

Naming Consistency3/5

Names are uniformly snake_case and some families share clear prefixes (es_tender_*, ask_pipeworx_*, polymarket_*). However, conventions are mixed: verb-led names like compare_entities and subscribe sit alongside noun phrases like entity_profile and bet_research, so there is no consistent verb_noun pattern.

Tool Count2/5

34 tools is already in the heavy range, but the bigger problem is scope: a server named 'Spain Tenders' ships 34 tools, only 3 of which are actually Spanish-procurement tools. The rest are a broad Pipeworx/Polymarket/utility toolkit, making the count inappropriate for the declared purpose.

Completeness3/5

The three es_tender_* tools cover the core discovery workflows: keyword search, recent notices, and status filtering with budgets, deadlines, and URLs. Notable gaps remain, though: no tender detail-by-id tool, no tender-specific subscription/alerting, and no explicit region, CPV, or date-range filters.

Resources