Skip to main content
Glama

Ver uma licitação

ver_licitacao
Read-onlyIdempotent

Detalhes de uma licitação aberta: objeto, órgão, prazos, valor, exigências, indícios e até 10 itens. Informe o slug ou o link da página (https://garimpopublico.com.br/licitacao/), que vem de buscar_licitacoes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ver_licitacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoEndereço da página da licitação no Garimpo Público
slugNoIdentificador da licitação no endereço da página

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful scope context (only 'aberta' bids, bounded to up to 10 itens) but says nothing about failure behavior for an unknown slug, precedence when both link and slug are provided, or pagination of the item list.

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, zero padding: the first front-loads what is returned, the second front-loads the identifier requirement and its source. Nothing is repeated from the schema or title.

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?

No output schema exists, and the description compensates by enumerating the returned fields. Given the schema marks zero required parameters, the sentence telling the caller to provide a slug or link is valuable disambiguation, though the definition could still be more complete about handling an invalid or ambiguous identifier.

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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds only the provenance hint (the value comes from buscar_licitacoes) and the URL template, which is mildly useful but does not clarify the slug-vs-link choice or the fact that neither parameter is required.

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?

States a specific verb and resource ('Detalhes de uma licitação aberta') and then enumerates exactly what the response contains: objeto, órgão, prazos, valor, exigências, indícios and up to 10 itens. It also contrasts implicitly with the search sibling by saying the slug comes from buscar_licitacoes, so the agent can separate lookup-by-id from search.

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?

Makes the usage path explicit: the slug/link 'vem de buscar_licitacoes', which tells the agent to search first and then call this tool for detail. There is no statement of when not to use it or what happens if neither identifier is supplied, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources