Skip to main content
Glama

Try an auto-reply without sending

test_auto_reply
Read-onlyIdempotent

A dry run: given a comment or direct message text (and optionally the account and the Shager post it's on), says which rule would answer it, first enabled match wins, oldest first, and exactly what would go out (public reply options, private message, link, file, the button step), and whether that account can send each part. Nothing is sent or recorded. Use it to check keywords and texts before asking your human to turn a rule on. Paused rules that would match are listed too.

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": {
      "workspace_id": "<workspace_id>",
      "trigger": "<trigger>",
      "text": "<text>"
    },
    "name": "test_auto_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe comment or message as a person would write it
post_idNoCOMMENT: the Shager post it's on; empty = a post the rule doesn't limit
triggerYes
channel_idNoThe account it arrives on; empty = any account
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses resolution order ('first enabled match wins, oldest first'), the output surface (public reply options, private message, link, file, button step, per-account send eligibility), and that paused matching rules are included. It also confirms the no-side-effect contract, which is the key behavioral fact for an agent deciding to call it.

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?

Front-loaded with 'A dry run' and the no-side-effect guarantee, and every clause carries meaning. However, the first sentence is a long run-on stacking parentheticals ('public reply options, private message, link, file, the button step'), which slightly hurts scanability.

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

Completeness5/5

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

No output schema exists, so the description must explain the return value, and it does in detail (matched rule, resolution order, each outgoing part, per-account eligibility). For a 5-param simulation tool this is complete enough for an agent to invoke confidently.

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?

With 80% schema description coverage, the schema already documents text, trigger, channel_id, and post_id meanings. The description restates that text is a comment/DM and that account and post are optional, but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource combination: a dry-run evaluation of an auto-reply rule against a given comment/message text. It immediately distinguishes itself from mutating siblings like create_auto_reply or update_auto_reply with 'Nothing is sent or recorded,' so an agent knows this is a simulation, not a send.

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?

Explicitly frames the use case: 'Use it to check keywords and texts before asking your human to turn a rule on,' which tells the agent the precondition (rule creation) and the purpose (validation). It does not name a specific alternative tool or state when not to use it, keeping it just below 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