Skip to main content
Glama

Delete a reminder to my human

reminder_delete
DestructiveIdempotent

Delete one reminder to your human for good. Its future emails stop and it cannot be restored. It frees a slot on the plan and works after the plan ended too. Returns deleted: true; an unknown or already deleted reminder_id answers reminder_not_found. To pause it or change it and keep it, use reminder_update.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "orm_exampleexampleexample2",
      "reminder_id": "rem_exampleexampleexample2"
    },
    "name": "reminder_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
reminder_idYesreminder id (rem_...) from reminder_create or reminder_list.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "orm_exampleexampleexample2",
      +    "reminder_id": "rem_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description still adds real context beyond that — future emails stop, the reminder cannot be restored, and a plan slot is freed. It also discloses the response shape (deleted: true) and the failure mode (unknown or already-deleted ids answer reminder_not_found), though it says nothing about auth scope or any confirmation requirement.

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?

Four short sentences, each carrying distinct information: effect, irreversibility, plan interaction, return values, and the sibling alternative. Front-loaded with the destructive consequence and no restating of the title or annotations.

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 3-parameter destructive delete with no output schema, the description covers what the agent needs: what is destroyed, that it is irreversible, what it returns, how failures surface, and which sibling to use instead. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so both required parameters are documented structurally, which sets the baseline at 3. The description earns an extra point by giving reminder_id semantic depth the schema lacks: an unknown or already-deleted id is not an error condition but a defined reminder_not_found response.

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?

States a specific verb and resource ("Delete one reminder to your human") and immediately distinguishes the outcome from sibling reminder_update by naming it. An agent can tell delete apart from pause/change without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this to permanently remove, use reminder_update "to pause it or change it and keep it." It also notes the operation remains available after the plan has ended, which is a real when-to-use condition rather than generic filler.

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.