Skip to main content
Glama
Sign In
CPFHub MCP Server

CPFHub MCP Server

Official
by cpfhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_person_by_cpf

Retrieve identity data (full name, gender, date of birth) from a Brazilian CPF number for verification.

Instructions

Retrieve identity data (full name, gender, and date of birth) from a Brazilian CPF number.

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

Input Schema

NameRequiredDescriptionDefault
cpfYesBrazilian CPF number (digits only or formatted as XXX.XXX.XXX-XX)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'retrieve' implying read-only, but does not disclose error handling, authentication needs, rate limits, or behavior on invalid CPFs. This is insufficient transparency.

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?

A single sentence with no wasted words, front-loading the key action and result. Very concise and efficient.

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 lookup tool with one parameter and no output schema, the description is mostly adequate. However, it does not mention error scenarios or return behavior for invalid CPFs, leaving some 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?

Schema coverage is 100% as the CPF parameter has a description. The tool description does not add extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 purpose: retrieving identity data (full name, gender, date of birth) from a Brazilian CPF number. It uses a specific verb and resource, and the sibling tool 'get_quota_information' is unrelated, so differentiation is implicit.

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?

The description implies the tool is for looking up a person by CPF, but does not provide explicit guidance on when to use it vs alternatives, no prerequisites, and no exclusions. It is adequate but lacks explicit context.

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

Deploy Server

Other Tools