Skip to main content
Glama

Monte statistics

Get a topic

get_topic
Read-onlyIdempotent

One topic in plain English: the idea, why it matters, a worked example, the usual trap, the formulas and the five lessons, with links.

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
topicYesTopic id from list_topics, like normal or clt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 the safety profile is fully covered externally. The description adds genuine value by disclosing the shape of the returned content, which matters since no output schema exists, but says nothing about behavior for invalid ids or unknown topics.

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?

One front-loaded sentence that enumerates the payload contents with zero filler. The trailing phrase 'and the five lessons' is slightly opaque but does not bloat the definition.

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, non-destructive read tool with no output schema, the description carries the important burden of telling the agent what comes back, and it does so thoroughly. The remaining gap is routing guidance against siblings, which is absent.

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 description coverage is 100% and the single parameter is an enum already explained as a topic id from list_topics with examples. The description adds no further semantics about the parameter, so the baseline 3 applies.

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 itemizes exactly what the single-topic payload contains (idea, motivation, worked example, common trap, formulas, lessons, links), which makes the resource concrete and implicitly distinguishes it from the list_topics catalog. It never states a retrieval verb outright, relying on the title and schema for that, so it falls just short of a clean verb+resource statement.

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 for looking up a single concept's explanation, whereas list_topics enumerates ids. There is no explicit statement of when to reach for this versus solve or search_terms, and the useful detail that the id comes from list_topics lives only 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