Skip to main content
Glama
xavimf87

mcp-govern

by xavimf87

cercar_contractes

Search public contracts from Catalonia's registry with filters for year, contract type, contractor, organism, and amount range. Retrieve details like description, award amount, and duration.

Instructions

Cerca contractes públics al Registre públic de contractes de Catalunya.

Permet filtrar per any, tipus, adjudicatari, organisme i import. Les dades inclouen: codi d'expedient, descripció, adjudicatari, import, data, durada, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNombre màxim de resultats (per defecte 50, màxim 50000)
offsetNoDesplaçament per a paginació
exerciciNoAny de l'exercici (ex: '2024')
organismeNoNom o part del nom de l'organisme contractant
adjudicatariNoNom o part del nom de l'adjudicatari
cerca_lliureNoText lliure per cercar a tots els camps
import_maximNoImport màxim d'adjudicació (€)
import_minimNoImport mínim d'adjudicació (€)
tipus_contracteNoTipus de contracte (ex: '5. SERVEIS', '1. OBRES', '3. SUBMINISTRAMENTS')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as read-only nature, pagination limits (max 50000 from schema), or data freshness. Only mentions output fields.

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 sentences: purpose, filters, output. Front-loaded and no fluff. Efficient for agent understanding.

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 9 parameters, 0 required, and existence of output schema, description is complete enough. Could mention registry source explicitly, but name implies it.

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 coverage is 100% with descriptions. Description lists some filters but adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states verb (cerca) and resource (contractes públics al Registre públic de contractes de Catalunya). Distinguishes from sibling tools like detall_contracte (detail) and boe_contractes (different source).

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?

Description lists filters but does not explicitly state when to use this tool vs alternatives like cercar_contractes_menors or other contract search tools. No guidance on when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xavimf87/mcp-govern'

If you have feedback or need assistance with the MCP directory API, please join our Discord server