Skip to main content
Glama

Able and Agent Sandbox

Answer in ACT chat

send_message
DestructiveIdempotent

Answer a Human in one conversation on any of your Principal's ACTs, as POST /api/v1/conversations/{id}/messages. The Human sees you as the Agent. Never put a door code in chat; it belongs in the access note.

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": {
      "conversation": "<conversation>",
      "body": "<body>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoYour key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read.
bodyYesWhat to say.
conversationYesThe conversation's id, cnv_….
idempotencyKeyYesOne string per errand or message you mean to send once, 1 to 255 characters of Latin-1 with no line breaks or other control characters: a retry with the same one does it once, never twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Any string, one per errand or message you mean to send once: a retry with the same one does it once, never twice."New value: +"One string per errand or message you mean to send once, 1 to 255 characters of Latin-1 with no line breaks or other control characters: a retry with the same one does it once, never twice."
  2. Changed3 schema fields changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Any string, one per thing you mean to do once: a retry with the same one does it once."New value: +"Any string, one per errand or message you mean to send once: a retry with the same one does it once, never twice."
    • addedInput schema / properties / idempotencyKey / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "conversation",
      -  "body"
      -]New value: +[
      +  "conversation",
      +  "body",
      +  "idempotencyKey"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/destructive profile, and the description adds genuinely new behavioral facts: the Human perceives the sender as the Agent, and door codes must never appear in chat but belong in the access note. That attribution and content-safety constraint are real operational context not derivable from annotations or schema. It does not describe what the call returns or what happens on a duplicate/error path, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and scope, then the identity note, then the safety rule. The REST path is arguably redundant detail for an agent, but nothing is padded or buried.

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?

For a simple 4-parameter send tool with full schema coverage and annotations covering idempotency and write semantics, the description supplies the essentials plus a non-obvious content constraint. The only gap is the return behavior (e.g. whether a message id comes back), which is absent since no output schema exists.

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 100% and each parameter (body, conversation, idempotencyKey, key) is documented in the schema itself. The description only adds the {id} placeholder mapping to the conversation parameter via the endpoint path; it contributes little else about parameter meaning, so the baseline 3 applies.

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?

States a concrete verb+resource: answering a Human in a single conversation on a Principal's ACT, and even names the underlying endpoint POST /api/v1/conversations/{id}/messages. It is clearly a write/send action, distinguishable from read-side siblings like list_messages, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'Answer a Human in one conversation' and 'on any of your Principal's ACTs', which scopes it to replying within an existing conversation. There is no explicit when-not guidance, no mention of when to prefer another tool, and no stated prerequisite (e.g. that the conversation must already exist).

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