gestaoclick_compras_delete
Compras: Deletar (DELETE /api/compras/{id}). [write, altera dados]
Bulk support: accepts ids for batched execution.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| ids | No | ||
| body | No | ||
| account | No |
GestãoClick
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
TDQS
C2.5/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description includes '[write, altera dados]', which indicates it modifies data, but the annotation destructiveHint is false, which contradicts the deletion action. This is a serious inconsistency, and the description does not clarify the safety profile despite being a delete operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (two sentences) and front-loaded with the main purpose. The second sentence about bulk support is useful, but the '[write, altera dados]' tag is redundant with annotations, adding little value. Overall, it's efficient with no unnecessary fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a mutation with no output schema and only 0% parameter coverage, the description is under-specified. It does not explain the effects of deletion (e.g., irreversible?), the role of 'account', or the response format, leaving the agent with gaps for safe use.
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?
The description mentions bulk support via 'ids' but does not explain the 'body' or 'account' parameters beyond the schema. With 0% schema description coverage, the description should clarify parameter usage, but it only highlights 'ids' briefly without syntax or semantics.
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 clearly states it deletes 'Compras' via DELETE /api/compras/{id}, identifies the resource and action. It distinguishes from siblings like gestaoclick_compras_get/list/update/create by the DELETE verb and 'Deletar' label, though it could be more explicit about bulk deletion as an alternative.
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 vs alternatives like gestaoclick_compras_update for modifications or gestaoclick_compras_delete for other resources. The only usage hint is the bulk support mention, but it lacks context on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.