Consulta o histórico veicular (SP) por CPF ou CNPJ do proprietário em base oficial. Dado cadastral do próprio titular.
| Name | Required | Description | Default |
|---|---|---|---|
| CPF | No | ||
| CNPJ | No | ||
| completo | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds context by specifying the official source and that it returns the owner's own cadastral data, which goes beyond structured data. No contradiction found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that is concise and front-loaded with the core purpose. No wasted words or redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only query tool with no output schema, the description covers essentials (what, who, scope) but lacks details on the 'completo' flag and the response structure. Given the official base and safety annotations, it is minimally complete but leaves gaps in parameter usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains that CPF and CNPJ refer to the owner, adding meaning to those parameters. However, the 'completo' boolean parameter is not described, and with 0% schema coverage, the description only partially compensates for understanding the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool consults vehicle history (SP) by owner's CPF/CNPJ in an official base. The verb 'Consulta' and resource 'histórico veicular' are explicit, and it distinguishes from sibling tools that focus on fines (multas) rather than full history.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage for vehicle history queries by owner identifier but does not explicitly state when to use it over alternatives like multas_veiculos_proprietario. No exclusions or when-not-to-use guidance provided, though the scope (SP) is mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The five multa-related tools are clearly distinct by resource (vehicle debts, history, federal infractions, CNH points, vehicles by owner), but the platform-level tools overlap: authenticate/connect/toolkit_info all touch connection/auth status, and marketplace bundles many separate capabilities into one broad tool. This creates some boundary confusion for an agent selecting between them.
Domain tools follow a consistent 'multas_' prefix pattern, but utility tools use inconsistent English verb/noun styles: authenticate, connect, marketplace, report_bug, show_version, toolkit_info. Mixing Portuguese noun-phrase names with generic English imperative/descriptive names makes the set feel disjointed and pattern-less.
Eleven tools is within a reasonable range, but it feels top-heavy because only five tools actually serve the core fines-consulta domain while the rest are platform/account/admin utilities. The huge marketplace tool also compresses many sub-operations into one entry, making the count misleading.
The core query workflow is covered: find vehicles by owner, query vehicle debts by plate, check federal infractions, and verify CNH points. Missing features like fine payment or appeal detail are beyond the stated consulta purpose, so there are only minor workaround-level gaps for the apparent scope.