Skip to main content
Glama

get_answer

Fetch the full answer for one knowledge-base question by id, exact question text, or path. Use an id from search_questions when possible. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoStable page id, e.g. edu-1-math-how-do-you-add-two-numbers
pathNoSite path or URL for the question, e.g. /education/1/math/how-do-you-add-two-numbers/
questionNoExact question or a known alternate phrasing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and it does disclose "Read-only", which is the most important safety fact. It says nothing about which of the three mutually optional parameters wins if several are supplied, what happens when all are omitted (required count is 0), or how an unknown id is reported — gaps that matter for a lookup tool.

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 what is fetched and by which keys, then the routing hint, then the read-only property. 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?

There is no output schema, so the description must convey the return value and it only offers "full answer", leaving format and shape unclear. For a zero-required-parameter tool with no annotations, the ambiguity around omitted or conflicting keys should have been addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, and the description earns extra by stating a precedence preference (id from search_questions first) that the schema does not encode. It does not explain the id-vs-path-vs-question resolution order beyond that single preference.

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?

States a specific verb (fetch) and resource (full answer for one knowledge-base question) plus the three accepted lookup keys, which makes it immediately distinguishable from search_questions, the sibling it names as the discovery counterpart.

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?

"Use an id from search_questions when possible" gives a concrete preference rule and implicitly routes discovery to the sibling tool. It stops short of stating what to do when no id is known (other than falling back to path/question) or when a lookup fails.

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