Skip to main content
Glama

Histórico Veicular SP

by io.github.mcp-dir

veiculo_historico_sp_consultar

Read-onlyIdempotent

Histórico dos veículos vinculados a um CPF ou CNPJ no estado de São Paulo. 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
CpfYes
CnpjYes
completoNo

Schema Changelog

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

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds meaningful context: no credentials needed, pay-per-query, access to public data, and LGPD data-controller responsibilities. This goes beyond the basic safety annotations without contradicting them.

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: it states the purpose first, then access/payment, data nature, and legal responsibilities. Every sentence contributes necessary information, with no fluff or repetition.

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?

The description is moderately complete for a query tool: it explains the source, access, and legal context. However, it omits details about the 'completo' parameter, the response format, and any pagination or filtering behavior. No output schema exists, so the description should provide more behavioral coverage.

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

Parameters1/5

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

Schema description coverage is 0% for all 3 parameters. The description only mentions 'CPF ou CNPJ' without explaining the parameters' format, the odd requirement of having both Cpf and Cnpj mandatory, or the purpose of the 'completo' boolean. The description does not compensate for the complete lack of 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 the tool's purpose: 'Histórico dos veículos vinculados a um CPF ou CNPJ no estado de São Paulo.' This is a specific verb+resource+scope, and it distinguishes the tool from the listed siblings (authenticate, connect, marketplace, etc.), none of which are similar data-query tools.

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 provides clear usage context: it is hosted by the platform, requires no credentials, and is paid via prepaid credits. It also clarifies that it accesses public information. However, it does not explicitly state when to use this tool versus alternatives, though no similar sibling tools exist.

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

All Histórico Veicular SP 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.8/5.0
Disambiguation4/5

Most tools have distinct purposes: authenticate is for login token, connect for status, marketplace for discovering/running MCPs, report_bug for feedback, show_version for versions, toolkit_info for installed state, and the domain-specific consultar tool. The only slight overlap is between authenticate and connect, as both relate to connection/auth, but their functions are clearly differentiated in the descriptions.

Naming Consistency2/5

Tool names follow no consistent pattern: single verbs (authenticate, connect), nouns (marketplace), verb_noun (report_bug, show_version), compound nouns (toolkit_info), and a snake_case domain-specific name (veiculo_historico_sp_consultar). Mixing conventions makes it hard to predict related tool names.

Tool Count4/5

Seven tools is within the typical well-scoped range. However, the server bundles broad platform utilities with a single domain-specific tool, creating a mismatch with the server name. Still, the count itself is reasonable for the actual functionality offered.

Completeness3/5

For the vehicle history domain, there is only one consult tool, which covers the basic query but lacks any supporting operations (e.g., history, status, or batch). The platform utilities are fairly complete but belong to a different purpose. This leaves notable gaps if the server is meant to be a cohesive vehicle-history service.

Resources