Skip to main content
Glama

Axad

Read a lesson page

read_page
Idempotent

Read one page of a lesson that has pages (a practice exam: one question and its text a page) and keep the learner's place there; for a lesson with no pages, read sentences from..to (at most 40). Returns the page text, or the numbered sentences.

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

Input Schema

NameRequiredDescriptionDefault
toNoNo pages: the last sentence number.
fromNoNo pages: the first sentence number.
pageNo0-based page; omit for the learner's current page.
materialYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false, and the description explains why: it 'keep[s] the learner's place there', i.e. the read mutates learner position state. That is exactly the kind of context annotations alone cannot convey. It also discloses the 40-sentence cap and the return shape, though it says nothing about error behavior for out-of-range page or sentence values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is packed into one long run-on sentence with an embedded parenthetical and an ambiguous 'from..to' notation. The core action is front-loaded, but splitting the paged and unpaged behavior into separate sentences would read considerably better.

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 states what comes back (page text or numbered sentences), and it covers the two modes and the sentence cap. The one substantive hole is the undefined required 'material' argument, which is material to calling the tool correctly.

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 75% and the schema already documents page as 0-based and from/to as sentence numbers. The description adds real value by scoping from/to to unpaged lessons and stating the at-most-40 limit, which the schema omits. However, the required 'material' parameter has no description in either place, leaving the agent to guess what it identifies.

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 states a specific verb and resource ('Read one page of a lesson') and distinguishes two operating modes: paged lessons (practice exam, one question per page) versus unpaged lessons read by sentence range. An agent can tell what the tool returns in each case, though the parenthetical example is a bit tangled.

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?

It gives a clear internal branch (use page for paged lessons, from/to for unpaged ones) and states that omitting page returns the learner's current position. It offers no guidance relative to the many show_* siblings (show_next, show_quiz, show_exam_task), so the agent must infer when this tool is preferred over them.

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.