Skip to main content
Glama

answer_question

Answers one ranked bibliometric question (e.g., Q8 or Q21) for a cached run, returning plain-language findings and result tables; enable prediction only when requested.

Instructions

Answer one ranked question, e.g. "Q8" (foundational papers) or "Q21" (interdisciplinarity). Returns findings (plain sentences) and result tables. The prediction questions Q24-Q34 are off unless prediction=True (only when the user asks for prediction).

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

Input Schema

NameRequiredDescriptionDefault
run_idYes
max_rowsNo
predictionNo
question_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does disclose useful behavior — the answer comes back as plain-sentence findings plus result tables, and Q24-Q34 are silently gated behind the prediction flag — but it says nothing about cost, latency, read-only vs. mutating nature, or what happens for an invalid question_id.

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 what the tool does and immediately followed by the output shape. Every clause carries information; only the return-format sentence partially duplicates the output schema.

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?

An output schema exists, so the brief return-value note is a bonus rather than a requirement. However, this is a required-parameter-heavy tool with zero schema documentation and no annotations, and the run_id scoping and max_rows truncation behavior remain unexplained — gaps an agent would hit on first invocation.

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 0%, so the description must compensate for all four parameters. It explains question_id well (via Q-code examples) and sets the exact default semantics for prediction, but leaves run_id (presumably an existing run from list_runs) and max_rows (row truncation of result tables) entirely undefined.

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 specific verb and resource ("Answer one ranked question") and illustrates the question_id domain with concrete examples ("Q8" foundational papers, "Q21" interdisciplinarity). The single-question scope distinguishes it from batch-style siblings, but it never names a sibling such as list_questions to clarify selection.

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?

Gives one explicit conditional: the prediction questions Q24-Q34 are off unless prediction=True and should only be enabled when the user asks for prediction. Beyond that gating rule, there is no guidance on when to pick this over list_questions or the run/report tools, so the agent must infer the workflow position.

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