Certificado Anbima

anbima_certificado_consultar

Read-onlyIdempotent

Consulta as certificações profissionais Anbima de uma pessoa a partir do CPF. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de ACESSO PÚBLICO em bases e fontes oficiais (a mesma disponível ao cidadão), não é dado privado nem sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

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": {
      "CPF": "<CPF>"
    },
    "name": "anbima_certificado_consultar"
  }
}

Input Schema

Name	Required	Description	Default
`CPF`	Yes
`completo`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: no credentials needed, prepaid credit billing, data is public access, and LGPD responsibilities. It discloses operational and legal aspects without contradicting annotations.

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?

The description is about three sentences long, front-loaded with the core purpose, then supplemented by payment, data-access, and legal context. Every sentence contributes operational value with no filler or repetition.

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?

For a simple CPF-lookup tool, the description covers the main purpose, data nature, and legal framing. However, it omits what the 'completo' parameter does and does not describe the return payload, and there is no output schema to fall back on. It's adequate but has clear gaps.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description only mentions CPF as the lookup key. The optional 'completo' boolean parameter is completely unexplained, and there is no format or default guidance. The description fails to compensate for the schema's lack of parameter documentation.

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?

The description clearly states the tool's function: it queries Anbima professional certifications for a person using their CPF. The verb 'Consulta' and resource 'certificações profissionais Anbima' are specific, and the tool is well differentiated from unrelated siblings like authenticate, marketplace, and report_bug.

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

Usage Guidelines4/5

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

The description provides useful context about when to use the tool: it's a hosted, prepaid, no-credentials lookup of public data. It doesn't explicitly name alternatives or state when not to use it, but the sibling tools are clearly unrelated, so the intended use is obvious. A clear exclusion or alternative would push it to 5.

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

All Certificado Anbima tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.