Skip to main content
Glama

Browse the glossary and learning path

browse_glossary
Read-onlyIdempotent

List ATLAS Explain's learning path (topics in order, each with its terms) or every glossary term in one group. Use it to suggest what to learn next, or to find the right term to explain.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_glossary"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional learning-path topic or glossary group, for example 'orders', 'risk', 'rates', 'futures'. Leave empty for the whole path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already cover the safety profile: read-only, idempotent, non-destructive, and closed-world. The description adds some return structure by saying topics are ordered and each includes its terms, but it does not describe pagination, limits, or exact term fields, so the added behavioral detail is modest.

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 sentences, front-loaded with the core listing behavior and followed by concrete usage guidance. There is no wasted wording or redundant restatement of the schema.

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 simple, read-only browse tool with one optional parameter and annotations covering safety, the description is largely sufficient. It explains the two browsing modes and usage contexts, though without an output schema it could say slightly more about what a returned term record contains.

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 optional `topic` parameter is already documented with examples and the empty-value behavior. The description reinforces that a topic maps to a learning-path topic or glossary group, but it adds little meaning beyond what the schema provides.

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 states a specific verb and resource: it lists the learning path with ordered topics and their terms, or every glossary term in one group. This clearly distinguishes the two browsing modes, though it does not explicitly name the `explain_term` sibling as the alternative for explaining a known term.

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?

It gives clear use cases: suggesting what to learn next, or finding the right term to explain. This provides context for when to browse rather than explain directly, but it does not explicitly state exclusions or name the alternative tool to use once a term is identified.

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.