Skip to main content
Glama

Delete your document or comment

heystack_delete
Destructive

Delete your document or comment. Requires MCP 2026-07-28.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "heystack_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile and repeat-call behavior are disclosed structurally. The description contributes a prerequisite (minimum MCP version), which is genuinely useful context an agent can't get from the schema. However, it says nothing about permanence, recoverability, or side effects on related content, which is a notable gap for an irreversible-sounding delete.

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?

Two short sentences with the operation front-loaded, so an agent can decide from the first clause alone. The version requirement is compact and earns its place as a hard prerequisite, though the phrasing is terse enough to read as boilerplate rather than deliberate guidance.

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?

Annotations cover destructiveness and idempotency, and there is no output schema to explain, which lowers the burden considerably. Still, for a destructive tool taking zero parameters, the definition never explains how the object to delete is determined, leaving the single most consequential detail unaddressed.

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?

The input schema declares zero parameters, so the baseline is 4 and there is no per-parameter meaning for the description to add. The description does not explain how the delete target is supplied, which is worth flagging, but with an empty schema there is no documented parameter this text could have elaborated on.

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 and resource ("Delete your document or comment"), which is enough for an agent to know this is the removal tool in a sibling set dominated by read/create/edit/list operations. It stops short of 5 because it doesn't say how the target is identified or how the document-vs-comment choice is made, so the scope of the operation remains slightly fuzzy.

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?

The only extra sentence is a version prerequisite ("Requires MCP 2026-07-28"), not usage guidance. There is no statement of when to delete versus when to use heystack_suggest_edit or heystack_comment, and no prerequisites or exclusion conditions are given. The title hints at scope but the description adds no when-to-use reasoning.

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