timeiq_expense_delete
Remove an expense entry by its unique ID to eliminate incorrect or unnecessary expenses.
Instructions
Delete an existing expense entry by ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| dry_run | No |
Remove an expense entry by its unique ID to eliminate incorrect or unnecessary expenses.
Delete an existing expense entry by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| dry_run | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description only states basic delete operation. Does not disclose side effects, permissions, reversibility, or behavior on non-existent ID.
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 sentence, concise but lacks structure. Could include information about dry_run parameter.
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?
Minimal description for a tool with no annotations, no output schema, and an undocumented boolean parameter. Does not provide enough context for safe use.
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?
Description mentions id parameter implicitly but does not explain dry_run parameter. Schema has 0% coverage, so description adds almost no value beyond parameter names.
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?
Clearly states the action (delete), resource (expense entry), and identifier (by ID). Distinguishes from sibling like timeiq_expense_delete_many by specifying single entry.
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 this tool vs alternatives like timeiq_expense_delete_many. Does not mention prerequisites or context.
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/Tomi2k/timeiq-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server