Skip to main content
Glama

Eurekuh

Delete a DM auto-reply

delete_dm_auto_reply
Destructive

Delete a DM auto-reply for good.

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": {
      "id": "<id>"
    },
    "name": "delete_dm_auto_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so 'for good' mostly restates existing structured data. Nothing is said about permissions required, whether the deletion is recoverable, or what happens to reply state/history associated with the removed auto-reply.

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?

A single short, front-loaded sentence with no filler. Brevity is achieved, though the minimalism contributes to the gaps elsewhere rather than being purely a virtue.

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

Completeness2/5

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

For an irreversible, destructive mutation with no output schema and an undocumented required parameter, the description should say more: how to source the id, what deletion affects, and why to prefer disabling. As written it leaves an agent guessing on each of those.

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?

Only 50% schema coverage: organizationId is documented in the schema, but the required 'id' has no description anywhere. The description does not explain where to obtain that id (presumably list_dm_auto_replies) or how it relates to the organization scoping, so it fails to compensate for the coverage 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?

States a specific verb and resource ('Delete a DM auto-reply') and adds 'for good' to signal permanence, so an agent can distinguish it from create_dm_auto_reply, list_dm_auto_replies and set_dm_auto_reply_enabled by name alone. It stops short of explicitly contrasting with those siblings.

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. Crucially, set_dm_auto_reply_enabled exists as an obvious non-destructive alternative (disable instead of remove), yet the description never mentions it, so an agent gets no help choosing between pausing and permanently removing a reply.

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