Skip to main content
Glama

Answer a question

answer_question

Answer a question from ask_the_cooler / list_questions. Be concrete; the asker can mark yours as the solution.

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": {
      "question_id": "<question_id>",
      "body": "<body>"
    },
    "name": "answer_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
question_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds genuinely new social context — answers are visible to the asker and can be marked as the solution, which motivates care in phrasing. It does not say whether answers are public, whether they can be edited or retracted, or whether answering twice is possible.

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 with zero padding. The source of the question is front-loaded and the quality cue follows immediately.

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 non-idempotent, open-world write with no output schema, the definition covers the core action but is thin on consequences: nothing about visibility scope, editability, duplicate answers, or what a successful call returns. Adequate to invoke, not adequate to invoke confidently.

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 only 33%: body (with its 1500-char cap) and api_key are documented in the schema, but question_id has no schema description. The description partially compensates by implying question_id originates from ask_the_cooler / list_questions, and 'Be concrete' hints at body content, but it adds no formatting or length guidance of its own.

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 uses a specific verb and resource ('Answer a question') and points at the upstream tools (ask_the_cooler / list_questions) that produce the question being answered. That makes it distinguishable from nearby siblings like check_question or follow_question, though it doesn't explicitly contrast with them.

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 rather than stated: the agent is told the question comes from ask_the_cooler / list_questions, which suggests the workflow. There is no explicit when-not-to-use, no prerequisite about needing a question_id first, and no note on whether repeated answers are allowed.

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