Skip to main content
Glama

Get topic

get_topic
Read-onlyIdempotent

Get sourced facts about one company, person or subject across all shows, grouped by episode, 20 facts per page by default. total is the topic's fact count; pass next_offset as offset for the next page.

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": "<topic>"
    },
    "name": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFacts per page, 1-50, default 20
topicYesTopic slug from list_topics, or its name (such as OpenAI)
offsetNoFacts to skip, default 0. Use next_offset from the previous page.

Output Schema

NameRequiredDescriptionDefault
nameYes
slugYes
factsYes
totalYes
offsetYes
episodesYes
returnedYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the burden is lighter, and the description still adds real context: results are grouped by episode, default page size is 20, and paging is driven by next_offset. It does not discuss rate limits or empty-result behavior, keeping it below a 5.

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?

Two dense sentences: the first front-loads the resource, scope, grouping and default page size; the second covers the pagination contract. Nothing is wasted and no information is buried.

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?

Given an output schema exists, the description need not explain return fields, and it covers the paging loop and default size that most affect correct invocation. It lacks any statement of when this tool is the wrong choice relative to search_facts, which is the main remaining gap.

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?

With 100% schema coverage the baseline is 3, and the description adds semantics beyond the schema by explaining that total is the topic's fact count and that next_offset is fed back in as offset, making the pagination contract concrete. The topic parameter's slug-or-name flexibility duplicates the schema, so no extra credit there.

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?

States a specific verb and resource: get sourced facts about one company, person or subject, across all shows and grouped by episode. Scope (all shows, grouped by episode) distinguishes it from per-episode or search-based siblings, though no sibling is named to route against 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?

Gives in-tool usage guidance for pagination ("pass next_offset as offset for the next page") but no when-to-use versus alternatives such as search_facts or list_topics, nor exclusion conditions. Usage is implied rather than directed.

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