Skip to main content
Glama

Eurekuh

Turn a DM auto-reply on or off

set_dm_auto_reply_enabled
Destructive

Pause or resume a DM auto-reply without deleting it.

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>",
      "enabled": "<enabled>"
    },
    "name": "set_dm_auto_reply_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
enabledYes
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

A3.7/5.0
Behavior3/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 the safety profile is covered structurally. The description adds the meaningful fact that the reply is preserved and the change is reversible in spirit, but it does not say what actually happens to in-flight or queued replies, nor whether enabling takes effect immediately.

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?

A single front-loaded sentence with zero filler; the distinguishing clause is placed where the reader needs it.

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?

For a simple toggle with three parameters and no output schema, the description is adequate but thin: it omits the boolean polarity and any note on effect timing, which are the two things an agent most needs before flipping a live setting.

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?

Schema coverage is only 33% — only organizationId is documented. The description maps 'a DM auto-reply' to id and 'pause or resume' to the enabled boolean, which is real added meaning, but it never states which boolean value means pause versus resume, leaving polarity to guesswork.

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?

The description gives a specific verb pair and resource ('Pause or resume a DM auto-reply') and implicitly rules out the deletion path with 'without deleting it', which separates it from delete_dm_auto_reply. It stops short of naming siblings explicitly, so it is clear but not fully differentiated.

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?

It states the operating context (temporarily toggling a reply while keeping it intact), which tells the agent to reach for this instead of deleting or recreating. No explicit 'when not to use' or prerequisite conditions are given, so it falls short of a 5.

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