quote_delete
Delete a specific quote from Qonto using its ID. Provide the quote UUID to remove it permanently.
Instructions
Delete a quote
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Quote ID (UUID) |
Delete a specific quote from Qonto using its ID. Provide the quote UUID to remove it permanently.
Delete a quote
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Quote ID (UUID) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only states the action without disclosing irreversibility, side effects, or required permissions.
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?
Single concise sentence, no wasted words, front-loaded.
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?
Adequate for basic function but lacks consequences (e.g., permanent) and error context.
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?
Schema coverage is 100% and the description adds no extra meaning beyond the schema's 'Quote ID (UUID)'.
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 'Delete a quote' clearly states the verb 'delete' and resource 'quote', distinguishing it from siblings like quote_create or quote_list.
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?
No guidance on when to use or not use this tool, such as prerequisites (e.g., quote must exist) or that deletion is irreversible.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexey-pelykh/qontoctl'
If you have feedback or need assistance with the MCP directory API, please join our Discord server