Skip to main content
Glama

Axad

Browse Axad's lessons

browse_catalog
Read-only

Browse Axad's library of lessons and practice exams. With no lang, returns the languages Axad teaches. With lang, returns the sections and lessons at path in that language's tree (an empty path is its top). For a learner who wants something to study or works toward an exam. Axad's API docs: https://axad.ai/developers.

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

Input Schema

NameRequiredDescriptionDefault
langNoBCP 47 code of the language to learn: "nl".
pathNoSection names from the top of the language's tree: ["Inburgering", "A2"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: the return shape depends on whether lang is supplied, and an empty path resolves to the top of the tree. It does not describe ordering, pagination, or depth of the returned lesson objects, which keeps it from 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?

Three tight sentences with the main purpose, the mode switch, and the audience front-loaded in that order; the trailing API docs link is a single useful pointer and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter, no-output-schema read tool, the description supplies the two pieces an agent most needs: how to choose a mode and what each mode returns. Remaining details (lesson object fields, ordering) are minor given the tool's simplicity and the annotations' coverage.

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 100%, so the baseline is 3, but the description goes further by explaining the semantic role of each optional parameter: omitting lang changes what the call returns entirely, and an empty path means the root of the language tree. That is meaning the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Browse Axad's library of lessons and practice exams") and then splits the behavior into its two distinct modes, so an agent can tell exactly what it returns in each case without opening the schema.

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 a clear selection rule between its own two modes ("With no lang... With lang...") and states the caller profile ("a learner who wants something to study or works toward an exam"). It does not name an alternative sibling tool or state when this is the wrong choice versus list_lessons or search_bag, so it stops short of a 5.

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.