Skip to main content
Glama

Latam Validate

Validate Cpf

validate_cpf
Read-onlyIdempotent

Validate a Brazilian CPF (Cadastro de Pessoas Físicas, the 11-digit personal tax ID) checksum. Pure computation, no lookup, returns whether the two check digits are correct and the formatted form. Punctuation (123.456.789-09) is accepted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cpf": "123.456.789-09"
    },
    "name": "validate_cpf"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpfYesThe CPF, e.g. "123.456.789-09" or "12345678909".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cpf": "123.456.789-09"
      +  },
      +  {
      +    "cpf": "12345678909"
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds substantive context beyond that: it discloses that no external lookup occurs (pure computation) and, in the absence of an output schema, states what is returned — check-digit validity plus the formatted form.

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?

Three short sentences, front-loaded with the purpose and followed by behavior and input tolerance. No filler or redundant restatement of the name.

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 single-parameter, side-effect-free validation tool with no output schema, the description covers purpose, computational nature, input format tolerance, and return shape. Nothing an agent needs to invoke it correctly is missing.

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% with examples in both formats, so the schema already carries the parameter meaning. The description's note that punctuation is accepted restates what the examples show, adding only marginal value over the schema.

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 verb and resource ("Validate a Brazilian CPF checksum") and disambiguates the resource against the sibling validators (validate_cnpj, validate_clabe) by naming the CPF and defining it as the 11-digit personal tax ID.

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?

Clarifies the operating context — pure computation, no lookup — and that both punctuated and bare formats are accepted, so an agent knows it can call it directly on existing data. It does not explicitly state exclusions or route to siblings, but the resource is narrow enough that this is minor.

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.