Skip to main content
Glama

buscar_licitaciones_publicas

Search public tenders and contracts published in the Third Section of the Argentine Official Gazette using keywords and date filters.

Instructions

Buscador especializado en licitaciones y contrataciones públicas en la Tercera Sección del Boletín Oficial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
criterioNoPalabra clave a buscar (ej. 'obras', 'alimentos', 'tecnología'). Por defecto busca 'licitacion'.
fechaDesdeNoFecha de inicio de búsqueda en formato DD/MM/YYYY (ej. '01/01/2026')
fechaHastaNoFecha de fin de búsqueda en formato DD/MM/YYYY (ej. '19/05/2026')
paginaNoNúmero de página para resultados de paginación
Behavior2/5

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

With no annotations, the description discloses only that it is a search engine. It fails to mention behavioral traits such as pagination behavior, result format, or any side effects.

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 a single sentence, front-loaded with the core purpose, and contains no unnecessary words.

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

Completeness2/5

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

Given the lack of an output schema, the description should hint at the return format or behavior, but it does not. It is insufficient for a search tool with 4 parameters.

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?

All parameters have full schema descriptions. The tool description adds no additional meaning beyond what the schema provides, so baseline score 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?

The description clearly states it is a specialized search engine for public tenders and contracts in the Third Section of the Official Bulletin, differentiating it from sibling tools that search other sections.

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 implies use for searching public tenders in the Third Section. It provides clear context but does not explicitly exclude other cases or name alternative tools, though siblings are separate.

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/voftec/bora-mcp'

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