Skip to main content
Glama

Niche of One Network

Academy

academy_browse
Read-onlyIdempotent

The Academy's courses, or one course's lessons in order, with which lessons are free to read.

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

Input Schema

NameRequiredDescriptionDefault
courseNo

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 readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered by structured data. The description contributes beyond that only by disclosing that lessons come back 'in order' and carry free/paid markers; with no output schema, it stops short of describing the actual response shape or structure.

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 dense sentence, front-loaded with the primary result set and then the parameter-driven variant. Nothing is wasted, though phrasing like 'with which lessons are free to read' is slightly compressed and could read more plainly.

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 one-optional-parameter read tool with rich annotations and no output schema, the description covers what is returned and how the parameter changes it, which is most of what an agent needs. Missing are the course identifier format and any hint about how free/paid status is represented, so an agent still guesses at invocation 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 0% for the single `course` parameter, so the description must carry the meaning — and it does explain the parameter's effect: supplying it switches the result from a course list to that course's ordered lessons. It does not state what form the course identifier should take (slug, name, or id), which is the remaining gap.

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 names the resource precisely ('The Academy's courses') and clarifies the two result shapes: all courses, or one course's lessons in order, annotated with which are free. An agent can tell it retrieves Academy content rather than mall/show/site content, though it never names the sibling 'academy_lesson' that might return a single lesson.

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 through the optional `course` parameter: omit it to get the course list, supply it to get that course's lessons. There is no explicit when-to-use vs. when-not, and no pointer to academy_lesson or other Academy-related siblings for retrieving a single lesson's content.

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