Skip to main content
Glama

Axad

Close a lesson

close_lesson
Idempotent

Close a lesson the learner finished or set aside. Its place, chats and cards are kept, and it no longer counts against the plan's active lessons; opening it again by its material id reopens it. Returns the lesson's state and the active count.

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": {
      "material": "<material>"
    },
    "name": "close_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYes

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?

Adds real behavioral context beyond the annotations: the lesson's place, chats and cards are retained, it stops counting against the plan's active lessons, and it can be reopened by material id. The annotations already declare idempotent=true and destructiveHint=false, so the description's job is to explain consequences, which it does well; it does not, however, restate idempotency or explain what happens to a lesson that is already closed.

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 sentences, front-loaded with the action and trigger, followed by retention/accounting effects and the return shape. No filler or repetition, and the reversal path is placed where an agent will read it.

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?

There is no output schema, and the description compensates by naming what is returned ('the lesson's state and the active count'). Combined with the stated side effects and reopen path, everything needed to call this one-parameter tool correctly is present.

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?

The single required parameter has 0% schema coverage, so the description must carry the load, and it does: 'by its material id' clarifies that 'material' means a material identifier rather than an object. It does not state the id's format or whether an unknown id errors, leaving a modest gap against the low coverage baseline.

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?

States a specific verb ('Close') and resource ('a lesson') plus the triggering condition ('finished or set aside'), and implicitly separates it from open_lesson by noting that opening again by material id reopens it. An agent can distinguish this from the sibling without reading either 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?

'Close a lesson the learner finished or set aside' gives a clear condition for when to invoke it, and the reopening sentence tells the agent the action is reversible rather than terminal. It stops short of naming an alternative explicitly, but the only sensible alternative (open_lesson) is clearly implied by the reopen instruction.

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.