Skip to main content
Glama

answer_prompt

DestructiveIdempotent

Submit answers to pending questions listed by list_pending, mapping question IDs to answer arrays for an agent. Resolve expired requests by re-reading pending questions instead of retrying.

Instructions

Answer a pending question from list_pending. Keys are question IDs, values are arrays of answer strings. An expired request returns openbot_conflict; read list_pending again instead of retrying.

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": {
      "agent": "<agent>",
      "requestId": "<requestId>",
      "answers": "<answers>"
    },
    "name": "answer_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent ID or exact name from list_agents
answersYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true and openWorldHint=true, and the description adds real context on top: the payload shape and a concrete failure mode (expired request returns openbot_conflict) with recovery instructions. It does not explain why the operation is flagged destructive or what state is consumed, which keeps it off 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and source, then payload format, then the error path. No filler or repetition.

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 mutating tool with a nested-object parameter and no output schema, the description covers input origin, payload shape and the main error branch. It stops short of describing success behavior or any permission requirements, but nothing essential to invoking it correctly is missing.

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 coverage is only 33%, and the description compensates for the hardest parameter by explaining that answers is keyed by question ID with arrays of answer strings. requestId is only indirectly covered via the list_pending reference, and the agent parameter is left entirely to the schema, so coverage is partial rather than complete.

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 and resource ('Answer a pending question') and anchors it to the sibling that produces the input ('from list_pending'), which cleanly separates it from list_agents, send_message and run_routine.

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?

The entry condition is explicit: the question must come from list_pending, so the agent knows to call that first. It also gives an explicit do-not-do ('read list_pending again instead of retrying') for the expiry case, though it does not contrast with send_message for free-form replies.

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