Skip to main content
Glama

Answer a projection's question

answer_question

Sends the user's answer to the projection's open question. Ask the user the question exactly as check_projection gave it, with its choices, and send the choice the user picked. Do not answer for the user. Needs the user's fovub sign-in.

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": {
      "run_id": "<run_id>",
      "seq": "<seq>"
    },
    "name": "answer_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
seqYesThe question's seq from check_projection.
answerNoThe user's choice, one of the question's choices.
run_idYesThe run_id that start_projection returned.
answersNoOnly for a question with several parts: each part's text mapped to the user's choice.
languageNoThe user's language as a BCP 47 code, such as es, es-MX, or fr: the language of the user's Claude account, or the language the user writes in. fovub then gives the questions, their choices, and the result's warning in that language. Leave it out for English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "The user's language as a BCP 47 code, such as es, es-MX, or fr: the language of the user's Claude account, or the language the user writes in. fovub then gives the questions, their choices, and the result's warning in that language. Leave it out for English.",
      +  "maxLength": 35,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so safety and side-effect class are known. The description usefully adds that a user sign-in is required and that the answer must come from the user, but it does not say what happens after submission (whether the projection resumes, whether the answer is final, or whether a duplicate submission is rejected given idempotentHint=false).

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, followed by the procedural instruction and the constraint. There is no redundant restatement of the name or title and no filler.

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 5-parameter mutation tool with a required human-in-the-loop step, the description covers the action, the prerequisite sibling call, the sign-off constraint and the auth requirement; there is no output schema to explain. The remaining gap is post-submission behavior, which an agent would need to know to decide whether to retry or re-ask.

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%, so run_id, seq, answer, answers and language are all documented in the schema itself. The description adds only a loose tie between the answer and the question's choices ('send the choice the user picked') and says nothing about when to use the multi-part 'answers' object or the language parameter, so the baseline of 3 applies.

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 description opens with a specific verb and resource: it 'sends the user's answer to the projection's open question.' That phrasing cleanly separates it from check_projection, which retrieves the question, so an agent can distinguish the read step from the write-back step without opening either schema.

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?

It explicitly tells the agent to ask the question exactly as check_projection gave it, including its choices, and to send the choice the user picked. The workflow prerequisite (call check_projection first) and the hard constraint 'Do not answer for the user' are both stated directly, leaving little to inference.

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