delete_auditDeletes the retained request metadata, generated report, and delivery record.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| accessToken | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| deleted | Yes |
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?
The description adds context beyond annotations by listing the specific data items destroyed (retained request metadata, report, delivery record). However, it does not disclose irreversible nature beyond what is implied by 'delete' or the 'destructiveHint' annotation. No additional behavioral details like permission requirements or side effects are provided.
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?
The description is a single concise sentence that immediately conveys the core action and targets. No extraneous information is included, and the structure is front-loaded and efficient.
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?
Given the presence of an output schema (handling return values) and annotations (destructiveHint, idempotentHint), the description covers the action adequately. However, it lacks context about reversibility, confirmation steps, or typical usage flow, which would benefit agent decision-making.
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 description coverage is 0%, and the tool description does not explain the 'id' or 'accessToken' parameters. The description only mentions what is deleted but fails to clarify the role of these parameters, leaving the agent without semantic understanding of required inputs.
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 action ('Deletes') and specifies the exact resources deleted (retained request metadata, generated report, delivery record). It distinguishes from sibling tools like 'estimate_audit' (which creates/estimates) and 'get_audit_status' (which retrieves status), making the tool's purpose unambiguous.
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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, conditions for deletion, or scenarios where deletion should be avoided. The agent must infer usage context from the tool name and description alone.
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.
Each tool has a distinct purpose: starting audits, deleting, estimating, status checking, listing checks, and starting paid audits. No functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., audit_url, delete_audit, estimate_audit). No mixing of conventions.
Six tools is a well-scoped set for an auditing service, covering the essential operations without unnecessary redundancy.
The tool surface covers the full audit lifecycle: estimation, free/paid start, status, and deletion. Minor gap: no tool to list all audits for a user.