Skip to main content
Glama

A class's dated lessons

list_class_lessons
Read-only

A class's lessons between two dates (default: the next 8 weeks), each with its status (on, closed, cancelled), places left and trial children.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe class's id.
toNoTo YYYY-MM-DD, in the business's own time zone.
fromNoFrom YYYY-MM-DD, in the business's own time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds meaningful context beyond that: the default date range and the per-lesson fields returned (status, places left, trial children); it does not mention pagination or limits, but the safety profile is well covered by annotations.

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?

A single sentence, front-loaded with the action and resource, then efficiently adding the default range and key return fields. There is no wasted wording.

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 simple read-only list tool with complete parameter documentation and annotations covering safety, the description gives enough context: date range default and the lesson attributes returned. No output schema exists, and the key returned fields are summarized adequately.

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%, and the schema documents id, from, and to with date format and timezone details. The description adds value by specifying that the date range defaults to the next 8 weeks, which is not stated in the schema.

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?

States a specific verb and resource: list a class's lessons between two dates, including statuses and available places. It is clear, but it does not name or contrast with close siblings such as list_branch_lessons, so sibling differentiation is implicit rather than explicit.

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?

Provides the useful default window (next 8 weeks) and implies the tool is for retrieving lessons for a given class. However, it does not say when to prefer this tool over list_branch_lessons, class_history, or other lesson-related siblings, nor does it give 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.

Resources