Consulta de Multas

multas_pontos_cnh

Read-onlyIdempotent

Consulta a situação da CNH (Carteira Nacional de Habilitação) pelo CPF do próprio condutor em base oficial: número de registro, categoria, validade e situação. É a mesma informação que o titular acessa nos canais oficiais (SENATRAN/DETRAN) para acompanhar a própria habilitação. Não expõe dado sigiloso de terceiros.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent hints. The description adds context that the data comes from official SENATRAN/DETRAN channels and is the same as the owner accesses, plus a privacy guarantee. No contradictions with 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?

Two sentences with no filler. The main verb and resource are front-loaded, and each sentence adds essential scope or privacy context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple query with two params, no output schema, and strong annotations, the description adequately covers purpose, scope, and data source. The main gap is the unexplained 'completo' parameter, which prevents a perfect score.

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?

Schema has 0% coverage and the description does not explain the optional 'completo' parameter. While CPF is implied, the 'completo' boolean is left ambiguous, and the description does not detail how it affects the query or response. The description only lists output fields, not parameter behavior.

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 queries the CNH status by CPF, listing the specific fields (registration number, category, validity, situation). It distinguishes from sibling tools about vehicle fines and history by focusing on the driver's own license.

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?

It indicates it's for the driver's own CPF and explicitly notes it does not expose third-party confidential data, implicitly telling agents not to use it for others' information. However, it lacks explicit comparison to sibling tools like 'multas_veiculos_proprietario'.

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

All Consulta de Multas 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.