Skip to main content
Glama

Read a research topic context

get_topic_context
Read-only

Retrieves source-backed claims, model inferences, disputes, gaps, and explicit beliefs for a topic, separating confirmed user beliefs from suggestions. Includes reference locators to trace sources.

Instructions

Read source-backed claims, model inferences, disputes, gaps and explicit beliefs.

    Confirmed user beliefs appear separately from model suggestions and candidates.
    References include version/block locators; get_claim expands their quotations.
    

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": {
      "topic_id": "<topic_id>"
    },
    "name": "get_topic_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
topic_idYes
max_claimsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds real behavioral context: confirmed user beliefs are returned separately from model suggestions and candidates, so the agent knows not to conflate evidence tiers, and references carry version/block locators for traceability.

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?

Three short sentences, front-loaded with what is returned and followed by the belief/provenance distinctions. No filler, though the stray leading/trailing whitespace and lack of an explicit statement about the required topic_id leave the structure slightly loose.

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?

An output schema exists, so return values needn't be spelled out, and the description adequately conveys the content categories and provenance model. However, for a tool whose only required parameter is entirely undocumented, the definition is not complete enough—an agent must guess whether topic_id is an internal ID or a name, and how max_claims truncates results.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions topic_id or max_claims. Neither the meaning of topic_id nor the default/capping behavior of max_claims (default 20) is clarified, so the description does nothing to compensate for the undocumented schema.

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 uses a specific verb ("Read") and enumerates the concrete payload of a topic context: source-backed claims, model inferences, disputes, gaps and beliefs. It partially distinguishes itself from the sibling get_claim by noting that get_claim expands the quotations found in references, though it never explicitly says it returns a topic's aggregated context keyed by topic_id.

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?

There is one useful routing hint: references carry version/block locators and get_claim should be used to expand their quotations. That implies a workflow (start here, drill down with get_claim) but the description never states when to call this tool versus search_sources or list_review_queue, nor any prerequisites or exclusions.

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