Search for specific text within TCE-PR portal areas by navigating up to 30 pages. Returns visited pages and identifies any failures during the search.
Busca texto navegando até 30 páginas de uma área. Expõe páginas visitadas e falhas; não é busca exaustiva.
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | inicio | |
| texto | Yes | ||
| max_paginas | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds behavioral context: it navigates up to 30 pages, exposes visited pages and failures, and is not exhaustive. This goes beyond annotations by specifying output behavior and bounds, though it does not detail error handling or exact return structure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy. The first states the core action and scope, the second adds output behavior and a limitation. Information is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter tool with 0% schema coverage and an output schema, the description covers the main action and key limitation (30 pages) but lacks parameter explanations and explicit output details (though output schema exists). The 'não é busca exaustiva' note is useful but does not compensate for missing parameter semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate for parameter meanings. It references 'área' and 'até 30 páginas' (implying max_paginas), but does not explicitly explain 'texto', 'area' valid values, or the relationship between max_paginas and the 30-page cap. The agent must infer parameter semantics, which is insufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb and resource: 'Busca texto navegando até 30 páginas de uma área' – search for text across pages of an area. It distinguishes from siblings like 'consultar_base_pr' by emphasizing navigation through pages rather than direct queries. The note 'não é busca exaustiva' further refines scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (searching text across pages) and provides a limitation ('não é busca exaustiva'), but it does not explicitly name alternatives or provide exclusion criteria. No contrast with sibling tools like 'ler_pagina_portal_pr' or 'consultar_licitacoes_pr' is given, leaving usage decisions to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.