Skip to main content
Glama

A module's content

module_content
Read-onlyIdempotent

Reads a module’s lessons and activities in teaching order, including objectives and formative items, and flags activities placed more than once.

Instructions

A module's activities and lessons in teaching order, each lesson with its activities in their own order, each activity with the objectives it targets and the items it uses formatively (for practice, not graded). Shows activities placed more than once.

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": {
      "moduleId": "<moduleId>"
    },
    "name": "module_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoA commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both.
branchNoThe branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both.
moduleIdYesThe module's id, as Module/local or the local part alone; list_modules gives them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: nesting and ordering guarantees, that items listed are formative/ungraded, and notably that activities placed more than once are shown — a disclosure that prevents wrong deduplication assumptions. It stops short of error or pagination behavior.

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 long but well-ordered sentence that walks the hierarchy from module to lesson to activity, followed by a short, high-value note about repeated placements. Dense but front-loaded and free of filler; the sentence could be split for readability but nothing is wasted.

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 carries the return-shape burden and does so effectively by describing the nested structure, ordering and the duplicate-placement caveat. Only minor gaps remain (error behavior on an unknown moduleId, or size/pagination expectations), which are not critical for a read-only lookup.

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 description coverage is 100% and all three parameters (ref, branch, moduleId) are documented in the schema, including the mutually exclusive ref/branch guidance and the Module/local id format. The description adds nothing about parameters, which is acceptable at full coverage — baseline 3.

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 ('A module's activities and lessons') and specifies its scope precisely: teaching order, nested lesson→activity ordering, targeted objectives and formative items. It is clear what the tool returns, though it never states a verb ('returns'/'lists') and does not contrast itself with lookalike siblings such as module_coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no named alternative. Nothing says whether to call this versus module_coverage, get_record or trace_record when the agent wants module-level teaching structure, so selection must be inferred from the title alone.

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