Skip to main content
Glama

Delete reminder

delete_reminder
Destructive

Permanently delete a reminder. This cannot be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reminder_id": "<reminder_id>"
    },
    "name": "delete_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
reminder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility warning in the description largely restates structured data. It adds no detail on authenticating, on whether the business_id must be resolved first, on cascade effects, or on what happens if the reminder is already completed — useful context that would have earned a higher score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the destructive consequence is right up front where an agent will read it before acting.

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

Completeness3/5

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

For a simple two-parameter destructive tool with annotations carrying the safety profile and no output schema, the description covers the essentials of what happens. It is still thin on error behavior (missing or already-deleted reminder) and never documents reminder_id, so it is adequate rather than complete.

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?

Schema coverage is only 50%: business_id is documented in the schema as coming from list_businesses and being optional for single-business connections, but reminder_id has no schema description at all. The description says nothing about either parameter, so it fails to compensate for the documented gap.

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 states a specific verb and resource ('Permanently delete a reminder') and adds the permanence qualifier, so its effect is unambiguous. It does not differentiate itself from related siblings such as complete_reminder or update_reminder, which is the only thing keeping it below a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. An agent is left to infer that complete_reminder or update_reminder are the non-destructive paths; the warning 'cannot be undone' vaguely implies caution but does not route to a sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources