Skip to main content
Glama

Consulta Veicular Estadual

by io.github.mcp-dir

veiculo_estadual_consultar

Read-onlyIdempotent

Dados de um veículo a partir da placa direto das bases estaduais de trânsito (DETRAN), incluindo débitos e situação do veículo. 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
PlacaYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds valuable behavioral context beyond annotations: payment per query, public access nature, and LGPD compliance responsibilities. This enriches the agent's understanding without contradicting 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?

The description is concise and front-loaded with the core purpose, followed by operational details (hosting, payment), then legal context. Each sentence carries meaningful information without fluff or redundancy. It is appropriately sized for the tool's complexity.

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?

The description covers the main purpose, data source, access credentials, payment model, and legal handling. It lacks details on return format and the behavior of the 'completo' parameter, but given no output schema and the tool's straightforward nature, it is reasonably complete. The 'completo' gap slightly limits completeness.

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?

With 0% schema description coverage, the description must explain parameters. It explains 'Placa' well ('a partir da placa'), but the optional 'completo' boolean is not described at all. Since there are only two parameters and one is left ambiguous, the description only partially compensates for the missing schema descriptions.

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 it queries vehicle data by plate from DETRAN state databases, including debts and vehicle situation. The verb 'consultar' is in the tool name, and the description specifies the resource and scope, distinguishing it from the unrelated sibling tools (authenticate, connect, etc.).

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 explains the hosting model, no credentials required, and prepaid credit per query, giving clear context on when to use this tool. It does not mention alternatives because there are no competing vehicle query tools among siblings, but it does not explicitly state exclusions or when-not-to-use scenarios.

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

All Consulta Veicular Estadual 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.9/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: authentication, connection status, marketplace operations, bug reporting, version info, toolkit state, and vehicle consultation. No two tools overlap in functionality, so an agent can reliably select the right one.

Naming Consistency2/5

Tool names are inconsistent, mixing English verbs (authenticate, connect, marketplace), verb+noun (report_bug, show_version), noun+noun (toolkit_info), and a Portuguese snake_case domain term (veiculo_estadual_consultar). No consistent convention is used across the set.

Tool Count3/5

Seven tools is a moderate count, but six of them are generic platform utilities unrelated to the server's stated vehicle-consultation purpose. The domain-specific surface is minimal, making the server feel padded with infrastructure tools.

Completeness4/5

For the domain of vehicle consultation, the single tool covers the core needs (lookup by plate with debts and situation). There are minor potential gaps, such as distinguishing different query types (e.g., by VIN), but the current surface is workable for a read-only consultation service.

Resources