Skip to main content
Glama

AIML Rounds

Browse contents

browse
Read-only

Browse the site's table of contents. No arguments: the 4 tracks with their parts and sections. With track: every section and lesson in it (optionally narrowed by part).

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoPart name within the track, e.g. 'Maths for ML', 'RAG', 'Agentic AI'
trackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds what annotations cannot: the shape of the returned outline and how it changes with arguments, which matters because there is no output schema. It doesn't cover edge cases such as an invalid part name.

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 compact sentences, front-loaded with the core purpose, then the argument-dependent behavior. Every clause carries information; nothing is redundant with the schema or annotations.

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 zero-required-parameter read tool with no output schema, the description supplies the essential return structure in both modes and the parameter interplay. Only minor gaps remain, such as behavior on unknown track/part values.

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?

Schema coverage is only 50% (part is documented, track is an undescribed enum). The description compensates by explaining that part optionally narrows within a track, implying the dependency between the two parameters, though it does not state what happens if part is supplied without track.

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?

"Browse the site's table of contents" gives a concrete verb and resource, and the two-mode breakdown (tracks → parts → sections/lessons) makes clear it is a structural navigation tool, distinct in spirit from leaf tools like get_lesson. It stops short of naming a sibling explicitly, so it lands just below the top mark.

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?

The description maps argument combinations directly to behavior: no arguments returns the 4 tracks with parts and sections, passing track returns every section and lesson, and part narrows within a track. That is clear usage context, but it offers no exclusions or comparison to search/roadmap for someone deciding between this and a lookup tool.

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