brasil-mcp-essentials

Official

by brasil-mcp

Overview Schema Source Related Servers Discussions Admin

Python

Local

validate_pis

Validates the format and check digit of Brazilian PIS/PASEP/NIT numbers to ensure data integrity.

Instructions

Valida PIS/PASEP/NIT (11 dígitos).

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": {
      "value": "<value>"
    },
    "name": "validate_pis"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as output format, error handling, or any side effects. It simply says 'validates,' which lacks detail for a mutation-free validation tool.

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 extremely concise (6 words) and front-loaded with the action and resource. Every word is essential; there is no fluff or redundant 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?

For a simple validation tool with one parameter and an output schema, the description is adequate but minimal. It does not mention what the validation result looks like, but the output schema presumably covers that. Could benefit from a brief note on return type.

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

Parameters4/5

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

The description adds meaning to the parameter beyond the schema by specifying that the input should be an 11-digit string (PIS/PASEP/NIT). This compensates for the 0% schema description coverage.

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?

The description explicitly states it validates PIS/PASEP/NIT (11 digits), which clearly identifies the resource and action. It distinguishes from sibling tools like validate_cpf and validate_cnpj by specifying a different identifier type.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description only states what it does, leaving the agent to infer usage context without explicit when-to-use or when-not-to-use instructions.

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