Skip to main content
Glama

Números gerais das licitações

numeros_gerais
Read-onlyIdempotent

Volume de licitações de saúde publicadas por semana no Brasil (desde a data de início), por categoria e os itens mais comprados. Com uf, inclui também as semanas daquele estado.

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": "numeros_gerais"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNoSigla do estado, ex.: PE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds context annotations cannot: the data is aggregated weekly, the window starts at the dataset start date, and the breakdown dimensions are category and top items. It does not state result limits or pagination, which keeps it below 5.

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 the scope and time granularity, then the optional-parameter behavior. No filler, though the second sentence could be tightened to remove the 'também' ambiguity.

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?

With no output schema and a single optional parameter, the description carries most of the burden and does describe the return dimensions (weekly volume, category, top items). Only volume limits and exact result shape are left unstated, which is a minor gap for a read-only aggregate tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining the effect of uf on the returned data (state-level weeks are included). The wording 'inclui também' is slightly ambiguous about whether state weeks are added alongside national weeks or replace them.

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 a specific resource and output shape: weekly volume of public health tenders in Brazil, broken down by category plus the most-purchased items. That is clearly an aggregate/statistics tool, distinguishable from record-level siblings like ver_licitacao or buscar_licitacoes, though no sibling is named explicitly.

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?

Usage is implied by the resource description (aggregate statistics over time), and the second sentence tells the agent what happens when uf is supplied. There is no explicit when-to-use vs. an alternative, and no statement of when not to use it.

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