Skip to main content
Glama

Reply in a conversation (older name)

pipeline_reply

Alias of pipeline_speak, kept so an agent written against the v1 protocol keeps working. Prefer pipeline_speak.

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": {
      "markdown": "<markdown>"
    },
    "name": "pipeline_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYes
thread_idNoDeprecated name for container_id.
container_idNo

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 readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the write/open-world profile is covered. The description adds genuinely new context by flagging the tool as a deprecated compatibility alias, but it says nothing about what actually happens when it is invoked (where the message lands, whether it is publicly visible, what a failure looks like).

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 short sentences, front-loaded with the identity of the tool and immediately followed by the routing recommendation. Nothing is padded or repeated.

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 legacy alias the minimal description is defensible, and the annotations plus the pointer to pipeline_speak cover the safety profile. However, with two of three parameters undocumented and no statement of the underlying effect, an agent still has to consult pipeline_speak to call this correctly.

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?

Schema description coverage is only 33%: thread_id carries 'Deprecated name for container_id' while markdown and container_id are undocumented. The description compensates for none of this, giving no hint about the content format for markdown or the relationship between thread_id and container_id.

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 identifies the tool as an alias of pipeline_speak kept for v1-protocol compatibility, which pairs with the title 'Reply in a conversation' to convey the underlying purpose. It never states the actual operation (posting a reply into a conversation) in its own words, so it relies on the reader resolving pipeline_speak, but it does clearly differentiate itself from that sibling by marking itself as the legacy name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Prefer pipeline_speak' and explains the sole condition for using this tool: an agent written against the v1 protocol. That is an unambiguous when-to-use / when-not-to-use statement with the alternative named directly.

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