Skip to main content
Glama

Metodologia dos indicadores

metodologia
Read-onlyIdempotent

Como cada número é calculado: a página de metodologia (fórmula, contas CVM, casos de borda). Use quando: "como vocês calculam o ROIC?"; "qual a metodologia do DY de FII?". NÃO use para: todas as fórmulas em JSON → dicionario; conferir números sorteados → auditar_amostra. Fonte e fórmula: https://dadosb3.com/metodologia, o mesmo texto do site. Retorna: sem nome: paginas; com nome (roic, roe, dividendos, fiis, multiplos...): conteudo em markdown. Vazio ou erro: nome desconhecido devolve erro: chame sem nome para a lista. Acesso: Gratuita, sem chave.

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

Input Schema

NameRequiredDescriptionDefault
nomeNoNome da página de metodologia (ex.: roic, dividendos). Vazio = lista as páginas disponíveis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / nome / description
      Added value: +"Nome da página de metodologia (ex.: roic, dividendos). Vazio = lista as páginas disponíveis."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds genuine context on top: source URL, that content mirrors the site text, free access with no key, and the error behavior for an unknown nome with the suggested recovery. Only minor gap is no note on content length or caching.

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?

Front-loads the purpose in one line, then uses labeled fragments (Use quando / NÃO use para / Retorna / Vazio ou erro / Acesso) that scan instantly. Every line carries distinct information; nothing is redundant with the title or schema.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description covers return shape (paginas vs conteudo in markdown), error handling, data provenance and access constraints. An agent has everything needed to call it and interpret both branches of the result.

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, but the description goes further: it names example values (roic, roe, dividendos, fiis, multiplos), restates that empty means listing pages, and documents the unknown-name error path — meaning beyond the schema's default="" note.

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 resource and scope: "Como cada número é calculado: a página de metodologia (fórmula, contas CVM, casos de borda)". It also explicitly separates itself from the two nearest siblings (dicionario for JSON formulas, auditar_amostra for checking sampled numbers), so the agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit "Use quando" examples ("como vocês calculam o ROIC?", "qual a metodologia do DY de FII?") plus a "NÃO use para" section naming the correct alternative tools for each excluded case. When-to-use, when-not-to-use and alternatives are all present.

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.