Skip to main content
Glama

Advance to next section

next_section
Read-only

Returns the next section in a finished teaching guide or an explicit completion result, advancing only on learner request or demonstrated understanding.

Instructions

Given the current section id in a finished guide, return the next section or an explicit completion result at the end. Advance only on learner request or demonstrated understanding.

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": {
      "guide_id": "<guide_id>",
      "section_id": "<section_id>"
    },
    "name": "next_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
guide_idYesFinished guide id (g_...).
section_idYesCurrent section id (s_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, closed-world read, so the description is not needed to establish safety. It does add genuinely new behavioral facts: what comes back (next section vs. an explicit completion result at the end) and the pedagogical precondition for advancing, both of which the annotations cannot express.

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, zero filler, with the input precondition front-loaded and the terminal behavior stated immediately after. Every clause carries information an agent would otherwise have to guess.

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

Completeness4/5

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

With no output schema, the description correctly takes on the burden of describing the return shape, including the end-of-guide termination case that an agent could otherwise misread as an error. It stops just short of saying what the completion result contains, which is the only remaining gap for a two-parameter navigation tool.

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

Parameters3/5

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

Schema coverage is 100%, so both guide_id and section_id semantics are already documented in the schema. The description reinforces that guide_id must be a finished guide and that section_id is the current position, but adds no format or ordering detail beyond that, so the baseline applies.

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 (return/advance) and resource (next section) scoped to a finished guide, and names the terminal case explicitly. An agent can tell this is sequential navigation rather than a read of an arbitrary section, though it does not name a sibling like read_section to make the distinction airtight.

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?

Gives a real usage condition — 'Advance only on learner request or demonstrated understanding' — plus the implicit prerequisite that the guide be finished and a current section id be supplied. It stops short of naming alternative tools for out-of-order access, so it is clear context rather than full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.