Skip to main content
Glama

Permanently Delete My Story

delete_story
DestructiveIdempotent

Permanently delete a story owned by the connected account. 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": {
      "storyId": "<storyId>",
      "confirmPermanentDeletion": "<confirmPermanentDeletion>"
    },
    "name": "delete_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyIdYes
confirmPermanentDeletionYesTrue only after the user explicitly confirmed permanent deletion of this story.

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 idempotentHint=true, so the safety profile is covered structurally. The phrase "This cannot be undone" reinforces the irreversibility in user-facing terms and "owned by the connected account" hints at an authorization scope, but the description adds little beyond the annotations.

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, zero waste, with the destructive consequence front-loaded in the second sentence. Nothing superfluous.

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?

No output schema is needed for a deletion tool and annotations cover the safety profile, so the core is adequate. However, the description never mentions the mandatory confirmPermanentDeletion pre-condition, leaving the agent to infer the two-step confirmation flow from the schema alone.

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 50%: confirmPermanentDeletion is documented in the schema, but storyId is not, and the description says nothing about either parameter. It notably omits the required explicit user-confirmation gate, which is a meaningful workflow constraint the agent needs to satisfy before calling.

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?

States a specific verb (delete) plus resource (story) and adds an ownership scope ("owned by the connected account"), which helps distinguish it from remove_story_from_world among the siblings. It does not explicitly name or contrast with that sibling, so it stops short of 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?

No when-to-use or when-not-to-use guidance. It says the action is permanent but never tells the agent to prefer remove_story_from_world (unpublish) or other alternatives when the user only wants the story hidden rather than destroyed.

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