Skip to main content
Glama

Axad

Learning paths

list_runbooks
Read-only

List Axad's learning paths (daily review, exam path, page by page, free-form chat), with the learner's place in each when signed in.

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

Input Schema

NameRequiredDescriptionDefault
langNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, non-destructive, closed-world listing, so the safety profile needs no restating. The description does add one genuinely new behavioral fact: the response includes the learner's position in each path only when authenticated. It says nothing about ordering, empty results, or whether signed-out callers get a different shape.

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?

One sentence, front-loaded with the action and resource, with the enumerated path types and the auth-dependent detail packed in without filler. Nothing is redundant or misplaced.

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

Completeness3/5

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

For a simple read-only listing with no output schema, the description is broadly sufficient about what is returned. The two remaining gaps are the undocumented lang parameter and the unspecified shape for signed-out callers, both of which an agent would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter (lang) is never mentioned in the description, so an agent gets no signal about what it accepts or what it localizes. With one undocumented parameter the description should have compensated and does not.

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 leads with a specific verb+resource ('List ... learning paths') and enumerates the four path types in parentheses (daily review, exam path, page by page, free-form chat), which tells an agent concretely what comes back. It does not explicitly distinguish itself from near neighbors like list_lessons or browse_catalog, so it falls short of a 5.

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?

The clause 'when signed in' implicitly sets the condition under which extra progress data appears, which is useful context. But there is no explicit when-to-use guidance, no statement of when a caller should prefer list_lessons or browse_catalog, and no exclusions.

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.