Skip to main content
Glama

Custom Solutions

Get an answer or note

get_answer
Read-onlyIdempotent

Full text of one published answer page (or blog note) by slug, with its FAQ and canonical URL.

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

Input Schema

NameRequiredDescriptionDefault
slugYesSlug from search_answers, e.g. 'what-is-aeo'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 a closed world, so the safety profile is covered. The description adds genuine value beyond them by disclosing the payload: full text, embedded FAQ, and canonical URL — which matters because no output schema exists. It omits failure behavior for unpublished or missing slugs.

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?

A single sentence with zero filler, leading with what is returned and following with the selector and the payload components. Nothing could be removed without losing information.

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?

For a one-parameter read tool whose annotations carry the safety profile, the description covers the return contents adequately in lieu of an output schema. Only the error/miss case for an invalid or unpublished slug is left unaddressed.

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% and the schema itself documents the slug format, pattern, length and a concrete example. The description only restates 'by slug', so baseline 3 applies; no additional semantics are contributed.

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 specific resource and selector: the full text of one published answer page (or blog note) identified by slug. It implicitly contrasts with the plural search_answers sibling by emphasizing 'one published' page, though it never names that alternative 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?

Usage is only implied — an agent can infer this is the fetch-by-slug counterpart to a search, but the description never states when to choose it over search_answers or what to do if the slug is unknown. The slug's provenance ('Slug from search_answers') lives in the schema, not the description.

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