Skip to main content
Glama

Preço de referência (amostra)

preco_referencia
Read-onlyIdempotent

Amostra do Garimpo Preços: o preço pago típico (mediana, Brasil) de um medicamento ou material de saúde nas compras públicas. Informe o item (nome) ou o slug. O detalhe por estado, fornecedores e compras é por convite ou assinatura.

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

Input Schema

NameRequiredDescriptionDefault
itemNoNome do item, ex.: "dipirona"
slugNoIdentificador do item, vindo de uma resposta anterior

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?

The annotations already declare this read-only, idempotent and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are a sample, the figure is a national median rather than a state-level or supplier-level breakdown, and richer detail is gated behind invitation or subscription. What is missing is any indication of the time window or currency of the price sample.

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?

Three short sentences, front-loaded with what the tool returns, then the input instruction, then the scope limitation. Every sentence carries distinct information with no restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations beyond the safety hints, the description must carry the return semantics, and it does only partially — it says the value is a median but not the currency, the reference period, or whether a sample size or confidence context accompanies it. For a two-parameter lookup tool this is adequate but leaves an agent guessing about what the number represents.

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 schema already explains both fields, setting the baseline at 3. The description adds real meaning by presenting item and slug as an either/or choice ("Informe o item (nome) ou o slug"), which the schema does not encode since neither parameter is required and no oneOf constraint exists — this tells the agent at least one identifier is expected.

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 uses a specific verb-plus-resource framing: it returns the typical price paid (median, Brazil) for a medicine or health material in public procurement. That is concrete enough for an agent to know it is a price-lookup tool, distinct in kind from the licitação-listing siblings. It does not explicitly name or contrast with any sibling, which keeps it below a 5.

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?

"Informe o item (nome) ou o slug" gives the calling precondition, and the note that state/supplier/purchase detail is only via invitation or subscription signals the tool's boundary. However, no alternative tool is named for cases where the agent needs per-purchase or per-supplier data, so the routing guidance remains implicit.

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