Skip to main content
Glama
Sign In

Spain Tenders

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Es Tender Search

es_tender_search
Read-onlyIdempotent

Keyword search over SPANISH government tender notices — Spain public procurement / licitaciones / contratación pública from PLACSP (Plataforma de Contratación del Sector Público, contrataciondelestado.es). Case-insensitive match against tender title (objeto del contrato), contracting body name (órgano de contratación), CPV classification codes, and expediente id. Use SPANISH keywords for best recall (e.g. "obras", "limpieza", "software", "energía", "ayuntamiento de madrid") since titles and buyer names are in Spanish; a CPV code prefix like "45" or "72" also works. Returns compact shaped contract notices with buyer, status, EUR amounts, CPV codes, procedure, deadline, and notice URL. Set pages: 2 or 3 to also walk older archive pages of the feed when the first page yields few matches.

Input Schema

NameRequiredDescriptionDefault
limitNoMax matching notices to return (default 20, max 100).
pagesNoHow many feed pages to scan, 1-3 (default 1 = ~185 latest notices). Each extra page adds ~185 older notices but also several MB of transfer — raise only when page 1 returns few matches.
queryYesKeyword(s), case-insensitive substring match. Spanish terms match best ("carreteras", "servicios de limpieza", "Generalitat"); a CPV code or prefix ("45", "72000000") matches the classification codes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "obras carreteras"
+  },
+  {
+    "limit": 20,
+    "pages": 2,
+    "query": "servicios de limpieza"
+  },
+  {
+    "query": "45"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds behavioral detail: case-insensitive matching, fields searched, returned notice fields, and pagination cost/behavior, which exceeds what annotations convey.

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?

Two sentences pack substantial information: source, fields, language guidance, pagination, and return shape. The second sentence is dense but every clause adds value; could be tightened slightly but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and no output schema, the description covers the data source, matching fields, language/code tips, pagination trade-offs, and returned fields. This is sufficient for an agent to select and invoke the tool correctly.

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 covers all three parameters with detailed descriptions, including examples and defaults. The description largely restates these (e.g., Spanish terms, pages behavior) without adding new semantic information beyond the 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 opens with 'Keyword search over SPANISH government tender notices', clearly stating the verb (search), resource (tender notices), and scope (Spanish government/PLACSP). It distinguishes from siblings like es_tender_by_status and es_tender_recent by focusing on keyword search across multiple fields.

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?

Provides explicit usage tips: using Spanish keywords for best recall, CPV prefix support, and adjusting pages when first page yields few matches. However, it does not explicitly name alternative tools or state when not to use this tool versus siblings like es_tender_by_status or es_tender_recent.

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