Skip to main content
Glama

search

Search Uruguayan legislation and official notices in the IMPO database. Filter results by norm type and year to locate specific documents.

Instructions

Search for normas or avisos in IMPO database.

Performs a search across IMPO's database of Uruguayan legislation and official notices. Results can be filtered by type and year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string (searches in norm titles and content)
tipoNoOptional filter by norm type (e.g., "ley", "decreto", "resolucion")
anioNoOptional filter by year
limitNoMaximum number of results (default: 50, max: 100)
ttlNoOptional TTL in seconds for cache. Defaults to 10 minutes (600s). Use 0 to bypass cache.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, cache behavior (though ttl parameter exists), or any side effects. The read-only nature of a search is implied but not explicitly stated, requiring the agent to assume based on the tool name.

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?

Two sentences, completely front-loaded with the main purpose. Every word serves a function. No extraneous information.

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 the existence of an output schema, the description is sufficiently complete for a search tool. It covers the core functionality and filtering options. Minor missing context like pagination defaults are handled by the schema.

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 well-described parameters. The description adds minimal value beyond the schema, essentially reiterating that results can be filtered. Baseline 3 is appropriate as the schema already does heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for normas or avisos in the IMPO database, using the verb 'search' and specifying the resource. It effectively conveys the tool's purpose, though it does not explicitly differentiate from siblings like 'norma' or 'bases'.

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?

The description mentions filtering by type and year, implying usage for legislative searches. However, it lacks explicit guidance on when not to use the tool or alternatives among siblings, leaving the agent to infer context.

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/daedalus/mcp-impo'

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