Skip to main content
Glama

Ver um órgão comprador

ver_orgao
Read-onlyIdempotent

Ficha pública de um órgão que publica licitações de saúde: resumo, licitações abertas, itens mais comprados e fornecedores. Informe o cnpj (14 dígitos) ou, para buscar, o nome com a uf.

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_orgao"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNoSigla do estado, ex.: PE
cnpjNoCNPJ do órgão, com ou sem pontuação
nomeNoParte do nome do órgão (exige uf)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description still adds value the annotations do not: it tells the agent what the payload contains (summary, open tenders, top purchased items, suppliers), which matters because there is no output schema. It does not cover failure modes for an invalid CNPJ or a name that matches multiple órgãos.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns and then how to invoke it, with no filler. Slightly dense packing of four content sections into one clause, but nothing that could be cut without losing 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?

For a read-only, three-parameter lookup with no output schema, the description carries the needed return-value information by naming the sections returned and the two ways to address an órgão. Only the ambiguity of multi-match name searches and error handling are left unaddressed.

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% and the schema already documents 'exige uf' on the nome field, so the description's 'o nome com a uf' largely restates it. The one genuine addition is framing the OR relationship between cnpj and nome+uf as two alternative identification paths; otherwise baseline 3 applies.

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 names the resource and its nature explicitly: 'Ficha pública de um órgão que publica licitações de saúde', and enumerates the content sections (resumo, licitações abertas, itens mais comprados, fornecedores). This clearly separates it from licitação-level siblings like ver_licitacao and buscar_licitacoes, though it never names an alternative.

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?

It states the two invocation modes and their conditions: identify by cnpj (14 digits) or, 'para buscar', by nome together with uf. That is clear context for how to call it, but there is no explicit when-not-to-use or pointer to the sibling tools that handle other entity types.

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