Skip to main content
Glama

painel

Read-onlyIdempotent

Retrieves a focused macroeconomic snapshot for a chosen topic, showing the current value, prior value, and 12-months-earlier value for comparing official Brazilian indicators.

Instructions

Retrato rápido de um tema: último valor, valor anterior e valor de 12 meses antes.

Args: tema: "geral" (principais indicadores do país) ou um tema do catálogo, ex.: politica_monetaria, inflacao, atividade, trabalho, fiscal, setor_externo, credito. Use buscar_indicadores sem argumentos para ver a lista.

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

Input Schema

NameRequiredDescriptionDefault
temaNogeral

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds the one thing annotations cannot: the exact shape of what comes back (last, prior, and 12-month-prior values), which matters because there is no output schema. It is silent on units, formatting, and what 'geral' expands to for multi-indicator output.

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?

The purpose is front-loaded in the first line, with argument detail correctly subordinated to an Args block. There is no filler, though the docstring-style formatting is slightly verbose relative to the tiny one-parameter surface.

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 single optional-parameter, read-only tool with no output schema, the definition covers purpose, valid argument values, the default, and a discovery path for the full catalog. The remaining gap — what 'geral' actually returns and in what units — is minor for a snapshot tool.

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 0% and the only parameter has a bare 'Tema' title with a 'geral' default, so the description must carry the burden — and it partly does by defining 'geral' as the country's main indicators and enumerating example theme slugs. The enumeration is explicitly partial ('ex.:'), so an agent still cannot know the full accepted value set without the extra discovery call.

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 first sentence names the operation concretely — a quick snapshot of a theme returning the latest value, the previous value, and the value from 12 months earlier. That is far more specific than a restatement of the name 'painel'. It stops short of contrasting with siblings such as obter_serie or comparar_series, which also return time-series values.

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?

It gives actionable guidance for the topic argument and, crucially, tells the agent to call buscar_indicadores with no arguments to discover the catalog. However, it never says when to prefer this over time-series tools like obter_serie, sgs_serie, or comparar_series, so the choice between them is left to inference.

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