Skip to main content
Glama

scores

Returns Piotroski F-Score (0–9) with each of the nine criteria broken out and the Graham criterion, so you can see the calculation behind the rating rather than just the number.

Instructions

Scores de qualidade e de valor de uma empresa da B3, critério por critério.

Devolve o Piotroski F-Score (0 a 9) com **cada um dos nove critérios
aberto**, dizendo qual passou e com que número, e o critério de Graham.
O objetivo é poder discordar do score: você vê a conta, não só a nota.

Parâmetros:
  ticker — código da ação na B3, em maiúsculas e com o dígito da classe.
    Exemplos: "WEGE3", "PETR4", "SANB11". Veja `listar_empresas`.
  chave_api — chave do Dados B3 (grátis, 200 consultas/dia, sem cartão).
    Dispensável para WEGE3, aberta em todas as ferramentas; necessária para
    as demais. Deixe "" para usar a variável de ambiente DADOS_B3_API_KEY,
    quando existir.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the free-tier rate limit (200 queries/day, no card), the auth requirement (key needed for all tickers except WEGE3, which is open everywhere), and the env-var fallback DADOS_B3_API_KEY when the key is left empty. What it omits is failure behavior — e.g. what happens with an invalid ticker or an exhausted quota — but auth and quota disclosure is above average for a read-only tool.

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?

Front-loaded with the purpose and return shape, then a clearly delimited 'Parâmetros' block, which is the right structure for a tool whose schema is undocumented. Every line is informative; the only mild slack is the parenthetical marketing aside about the key being free with no card, which is useful but could be trimmed.

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 two-parameter read tool with no annotations and no output schema, the description supplies everything an agent needs: the ticker format and examples, the credential rules including the free-tier limit and env-var fallback, and a description of the returned structure (per-criterion pass/fail with numbers, plus Graham). Nothing material is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must do all the work, and it does: ticker is specified as uppercase with the class digit plus three concrete examples and a pointer to `listar_empresas` for discovery, and chave_api explains its default empty string, its env-var fallback, and exactly when it is required versus optional. This adds substantial meaning that the bare schema (title-only properties) does not carry.

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?

States a specific verb and resource — quality/value scores for a B3 company, criterion by criterion — and specifies the concrete payload (Piotroski F-Score 0-9 with all nine criteria opened, plus the Graham criterion). It implicitly differentiates itself from a summary-style sibling ('você vê a conta, não só a nota'), but never names 'veredito' or 'metodologia' explicitly, so routing among the score-related siblings is left partly to inference.

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?

There is no explicit when-to-use / when-not-to-use section and no named alternative among the ~30 siblings. The sentence about being able to disagree with the score because the calculation is exposed implies the use case (auditing a score rather than just reading a grade), and the chave_api note gives conditional usage guidance, but the agent must infer the rest.

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