Skip to main content
Glama
agent-runbooks

throng

by agent-runbooks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

send_message

Send follow-up messages to an existing agent session and return its turn result; queue background work or steer an active run.

Instructions

Sends the next message into an earlier session (session_id from run_thronglet) and returns the same JSON as run_thronglet. A message to a session whose turn is still running waits for that turn to end: turns on one session never overlap. With background: true the call returns {session_id, state, queued} as soon as the turn runs; collect the result with wait_thronglet. steer: true interrupts the running turn and delivers this message next; queued messages follow it. A session its harness cannot continue (resume or load) takes no further message, steer included: list_thronglets shows it as accepts_messages: false.

Input Schema

NameRequiredDescriptionDefault
steerNoInterrupt the running turn (session/cancel) and run this message as the very next turn, ahead of queued messages. The in-flight tool call is aborted; a half-applied edit may remain.
promptYesNext message for the agent
schemaNoJSON Schema (draft-07 or 2020-12) for structured output: the agent ends with a matching JSON value as its final message, returned as `structured` instead of `text`
timeout_sNoWall-clock limit for the run in seconds; default from config (21600)
backgroundNoReturn as soon as the turn is running (or queued behind the session's current turn); collect the result with wait_thronglet
session_idYessession_id from run_thronglet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / schema / description
      Previous value: -"JSON Schema (draft-07 or 2020-12) for structured output: the agent submits a matching result, returned as `structured` instead of `text`"New value: +"JSON Schema (draft-07 or 2020-12) for structured output: the agent ends with a matching JSON value as its final message, returned as `structured` instead of `text`"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: turns never overlap, a message waits for the running turn, background returns {session_id, state, queued}, steer aborts the in-flight tool call and may leave a half-applied edit, and sessions whose harness cannot resume/load accept no messages at all. These are exactly the non-obvious behaviors an agent needs.

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?

The purpose and return shape are front-loaded in the first sentence, and no sentence is filler. However, several sentences pack multiple clauses (waiting semantics, steer ordering, harness failure) and require re-reading, which costs some clarity.

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?

There is no output schema, but the description supplies the return shapes itself (same JSON as run_thronglet, or {session_id, state, queued} in background mode) and covers the failure case for non-resumable sessions. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-parameter meaning is already documented and a baseline of 3 applies. The description goes beyond the schema by explaining cross-parameter behavior: queued messages follow a steer, and the result of a background call must be collected with wait_thronglet.

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?

The first sentence states a specific verb+resource+scope: it sends the next message into an earlier session identified by a session_id from run_thronglet, and it returns the same JSON as run_thronglet. This clearly separates it from run_thronglet (which creates the session) and from the other siblings.

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 gives clear context for use: message an existing session, use background:true to return early and collect via wait_thronglet, use steer:true to interrupt a running turn. It implies but never explicitly states the alternative (start a new session with run_thronglet), so routing guidance is strong but not fully spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools