Skip to main content
Glama
eddmann

intervals-icu-mcp

by eddmann

delete_activity

Delete an activity permanently from Intervals.icu by its unique ID. This irreversible action requires caution.

Instructions

Delete an activity permanently.

Permanently removes an activity from your account. This action cannot be undone. Use with caution.

Args: activity_id: The unique ID of the activity to delete

Returns: JSON string with deletion confirmation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYesActivity ID to delete

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does so excellently. It discloses that the operation is permanent, cannot be undone, and returns a JSON string with deletion confirmation, covering the key behavioral trait of irreversibility.

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 well-structured with a title, body, and Args/Returns sections. However, the first three sentences are somewhat redundant ('Delete', 'Permanently removes', 'cannot be undone' all convey irreversibility), making it slightly less concise than ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter delete operation with an output schema, the description is fully self-contained. It covers the operation, consequences, parameter, and return type, requiring no additional context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds minor wording ('unique ID', 'to delete') that slightly clarifies but does not provide substantive new meaning beyond the schema's 'Activity ID to delete'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action as 'Delete an activity permanently' and explicitly states it 'Permanently removes an activity from your account', distinguishing it from sibling tools like update_activity or delete_event. The resource and verb are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool by emphasizing permanence and irreversibility ('This action cannot be undone') and advising 'Use with caution.' It does not explicitly name alternatives, but the context strongly implies this is for irreversible deletion only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eddmann/intervals-icu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server