Skip to main content
Glama

Full answer to a question

get_answer
Read-onlyIdempotent

Returns the full text of one of Advisorn's questions and answers (short answer, sections, legal references, related questions, page link), by id from search or list_topics.

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": {
      "id": "<id>"
    },
    "name": "get_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesQuestion id, e.g. sof-what-is.
langNoLanguage of the answer: en, it, de or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the payoff: a detailed breakdown of returned fields, which matters because there is no output schema. Minor gap: it doesn't say what happens for an unknown id or when a translation is unavailable.

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?

A single front-loaded sentence with no filler, and the return-content list earns its space because no output schema exists. The parenthetical enumeration is a bit dense but readable.

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

Completeness4/5

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

With no output schema, the description takes on the job of explaining return contents and does so explicitly. The remaining gap is language behavior (default en, fallback when a translation is missing), which an agent would want to know before calling with lang.

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 100%, so both id and lang are already documented with an example and an enum, establishing the baseline of 3. The description's only addition is the provenance of the id ('from search or list_topics'), which is genuine but small; the lang parameter is not elaborated at all.

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 ('Returns') and resource ('full text of one of Advisorn's questions and answers'), then enumerates what the answer contains (short answer, sections, legal references, related questions, page link). It also names the id source, so an agent can tell it apart from search and list_topics without opening a schema.

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?

'by id from search or list_topics' establishes the required workflow: discover an id with a sibling tool, then fetch the full record here. There is no explicit when-not guidance, but the retrieval-vs-discovery split is clear enough that the agent will not reach for this tool to browse.

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