Skip to main content
Glama

CarlNotes

Delete a hot take

delete_hot_take
DestructiveIdempotent

Delete a hot take on CarlNotes with its replies, for good. Its author, the topic's owner, and an admin may delete it. Use it when the user asks Carl or CarlNotes to delete my hot take, remove this comment, or take down a reply on my topic.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "delete_hot_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe hot take's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, but the description adds substantive behavior: deletion cascades to replies, it is permanent ("for good"), and it is restricted to the author, the topic owner, or an admin. That authorization model is not derivable from the schema or annotations. It could go further on failure behavior when the caller lacks permission.

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 sentences, front-loaded with the action and its blast radius, then the permission rule and trigger phrasings. No redundant restatement of the title or schema.

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

Completeness4/5

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

For a destructive one-parameter tool with no output schema, the definition covers scope, permanence, cascade, and authorization — the essentials an agent needs before calling it. Only the outcome of an unauthorized or already-deleted call is left unspecified.

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?

The single parameter is fully documented in the schema at 100% coverage, so the baseline is 3. The description adds only indirect semantics — mentioning deleting "a reply on my topic" implies comment_id may refer to a reply as well as a top-level hot take.

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 a hot take on CarlNotes") plus the cascade scope ("with its replies, for good"). It is unambiguous which entity is affected and clearly distinct from post_hot_take or delete_note, though it does not explicitly name delete_note as the non-equivalent sibling.

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?

Provides concrete trigger phrasings — "delete my hot take", "remove this comment", "take down a reply on my topic" — which map user language onto this tool. It does not state when to prefer an alternative (e.g. editing or reporting content via report_content) or when not to use it, so it stops short of explicit exclusion guidance.

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.