Skip to main content
Glama

Receita Federal PF

by io.github.mcp-dir

receita_pf_consultar

Read-onlyIdempotent

Consulta a situação cadastral de uma pessoa física na Receita Federal a partir do CPF e da data de nascimento. 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CpfYes
completoNo
DataNascimentoYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

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 these: payment requirements, public data classification, and LGPD compliance. This helps an agent assess suitability and legal responsibilities.

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 main purpose is front-loaded in the first sentence. The following sentences add operational (payment, hosting) and legal (public data, LGPD) context without redundancy. It is slightly longer than strictly necessary but every sentence carries information.

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?

The tool is simple, and annotations cover safety. The description covers purpose, inputs, payment, and legal constraints. However, it lacks any description of the return value (no output schema) and leaves the 'completo' parameter unexplained, creating meaningful gaps.

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?

The description explains the role of CPF and DataNascimento as inputs, aligning with required schema fields. However, it does not clarify the optional 'completo' boolean parameter, and no format constraints or examples are given. With 0% schema coverage, this is a partial gap.

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 action: consulting the registration status of an individual in the Federal Revenue using CPF and birth date. This specific verb+resource+input distinguishes it from sibling tools like authenticate or marketplace.

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 rich context on when to use the tool: hosted by the platform, no credentials required, pay-per-query with prepaid credit, and it accesses public data. It does not explicitly mention alternatives, but the usage context is clear and actionable.

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

All Receita Federal PF toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool serves a clearly distinct purpose: authentication, connection status, marketplace operations, CPF query, bug reporting, version info, and toolkit state. There is no meaningful overlap or ambiguity between any of the tools.

Naming Consistency2/5

Naming is inconsistent: some tools are single verbs (connect, authenticate), some are verb_noun (report_bug, show_version), one is a noun (marketplace), one is a noun phrase (toolkit_info), and one mixes Portuguese and English in an unusual order (receita_pf_consultar). The lack of a clear pattern hurts predictability.

Tool Count4/5

Seven tools is a reasonable count for this server, which appears to be a general MCP platform toolkit with a single domain-specific CPF query tool. The count is neither too thin nor bloated, though the mix of platform admin tools with one domain tool is slightly unusual.

Completeness2/5

For a server named 'Receita Federal PF', the only actual domain operation is a single CPF status consultation. There are no other tax-related operations (e.g., CNPJ queries, tax debt checks, or receipt management), leaving significant gaps for anyone expecting a comprehensive Receita Federal integration. The platform admin tools are complete, but they don't fulfill the apparent domain purpose.

Resources