Skip to main content
Glama

askround_answer

Retrieve one stored answer by its round and answer ID to read its full text and sources, or return only the passage around a quote for a quick fact check.

Instructions

One answer from a round already asked, by the id a brief gives ('openai#2'): its full text and sources, or with around only the passage around that quote - the cheap way to check a fact.

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": {
      "round": "<round>"
    },
    "name": "askround_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
runNo
roundYesthe round's directory, as the brief's 'round' gives it
answerNothe answer's id, e.g. 'openai#2' or 'openai@BR#2'
aroundNoa quote: return only the passage around it
localeNowhen the round was asked in several locales
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral load. It implies a read-only fetch and discloses what comes back (full text and sources, or just the passage with `around`), which is genuinely useful, but it says nothing about what happens when `answer` is omitted, error behavior for a missing id, or how locale/provider affect the result.

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?

It's a single dense sentence with a parenthetical example, front-loaded with the main purpose and the cheap-mode hint. Slightly compressed but every clause carries information; no filler.

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 6-parameter tool with no output schema and no annotations, the description covers the core fetch and the `around` shortcut but leaves the optional `run`, `locale`, and `provider` parameters and the default behavior when `answer` is absent unexplained.

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 67%, so the baseline is 3. The description reinforces the `answer` id format and the meaning of `around` (passage-only retrieval), but those are already in the schema descriptions, and it adds nothing for `run`, `locale`, or `provider`.

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 names a concrete retrieval action and resource: one answer from an already-asked round, keyed by an id like 'openai#2', returning full text plus sources. It implicitly separates itself from asking (askround_ask) by saying the round is 'already asked', but it never names a sibling tool 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?

It supplies a use case ('the cheap way to check a fact') and distinguishes the cheaper `around` mode from the full-text mode. It gives no exclusions or named alternatives, so an agent still has to infer when another sibling such as askround_report or askround_diff is a better match.

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