Skip to main content
Glama

Answers a question from the given text only

text_answer
Read-only

Answers a question from the given text only (max 30,000 characters), with supporting quotes and their character offsets. Each quote is checked against the text and dropped if it does not occur in it. answerable is false when the text does not contain the answer. Model output: verify before relying on it. Related tools on this server, for a different need: text_chunk when you need to generate overlapping text chunks with character offsets; text_diff when you need to find differences between two texts by line, word or character. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "<question>",
      "text": "<text>"
    },
    "name": "text_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe only source for the answer (max 30,000 characters)
questionYesQuestion to answer (max 500 characters)

Output Schema

NameRequiredDescriptionDefault
noteNo
answerNo
quotesNo
questionNo
checkedAtNo
answerableNo
quotesDroppedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{}
    • addedOutput schema / properties / answerable
      Added value: +{}
    • addedOutput schema / properties / checkedAt
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / question
      Added value: +{}
    • addedOutput schema / properties / quotes
      Added value: +{}
    • addedOutput schema / properties / quotesDropped
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint openWorldHint annotations, the description discloses verification behavior (quotes checked and dropped if absent), the answerable=false failure mode, a caution that model output must be verified, and the billing model including that failed calls are not charged. For a paid, open-world tool this is unusually complete behavioral disclosure.

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?

The critical constraints (source-text-only scope, size limit, output shape) are front-loaded and each sentence carries information. The closing pricing sentence is somewhat padded by the network enumeration ('Base, Solana and 10 more networks'), which is detail an agent rarely needs to select or call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need only cover selection and behavioral caveats, and it does so: input limits, quote verification, the unanswerable case, trust warning, and cost. Nothing an agent needs to call this 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 description coverage is 100%, so both parameters are already documented, and the description only restates the 30,000-character text cap that the schema carries. No additional syntax or format guidance is added beyond the structured fields, making the baseline 3 appropriate.

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 opening sentence gives a specific verb and resource ('answers a question from the given text only') plus scope and output form ('with supporting quotes and their character offsets'). An agent can distinguish it from text_chunk and text_diff without opening any schema, since those are explicitly framed as different needs.

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?

It routes the agent to alternatives, naming text_chunk for chunk generation and text_diff for diffing, which are the closest siblings. It stops short of stating explicit when-not-to-use conditions for this tool itself (e.g. very long documents, or when no source text exists), so it is clear but not fully exhaustive.

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