Skip to main content
Glama

get_reply_variants

Read-onlyIdempotent

Ready-made wording for an automation, drawn at random from reeldrop's shared library: kind="comment_reply" for the public replies under a comment ("Check your DMs!"), or kind="dm_message" for the DM text itself.

count is 1–50. Pass exclude (the messages the automation already has) so each call tops the list up with new ones instead of repeating. Nothing is generated, so it is instant and free of AI usage. Offer a handful to the user to choose from rather than adopting them silently, and put the chosen text into create_automation / update_automation (public_reply_messages / private_dm_messages). Automations rotate their messages, so several different variants read as less repetitive than one.

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>",
      "kind": "<kind>"
    },
    "name": "get_reply_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
countNo
excludeNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds useful behavior beyond the annotations: variants are drawn at random, nothing is AI-generated, calls are instant and free, and exclude tops up existing messages instead of repeating them. The read-only and non-destructive profile is consistent with the annotations, but auth, rate limits, and workspace scoping are not discussed.

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?

The description is front-loaded with purpose and then efficiently layers in kind selection, count, exclude behavior, and user workflow. Every sentence contributes information needed to invoke the tool correctly.

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?

With an output schema and safety annotations already present, the description covers most of what an agent needs: purpose, randomness, exclude behavior, and downstream placement of results. The main gap is the lack of any explanation for workspace_id.

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 description coverage is 0%, so the description must carry parameter meaning. It explains kind, count (1–50), and exclude well, but it does not explain workspace_id at all, leaving one required parameter without added semantics.

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 resource and behavior: ready-made reply wording drawn at random from a shared library for automations. It also explains the two kind values, comment_reply and dm_message, which makes the tool's purpose concrete and distinguishable.

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?

Gives clear usage context: choose kind based on public comment replies versus DM text, pass exclude to avoid repeats, offer variants to the user, and place chosen text into create_automation or update_automation. It lacks explicit when-not-to-use guidance or named alternatives, 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