Skip to main content
Glama

Read a lesson

read_pain_lesson
Read-only

Returns the content and key takeaways of one Recalibrate Academy lesson so it can be taught in the conversation. Use a lesson_id from find_pain_lessons.

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": {
      "lesson_id": "<lesson_id>"
    },
    "name": "read_pain_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
lesson_idYeslesson_id from find_pain_lessons

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the payload includes content plus key takeaways, which tells the agent something about the response. It says nothing about error behavior for a bad lesson_id or any size/truncation characteristics.

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 short sentences, front-loaded with what is returned, followed by the prerequisite for the single parameter. No wasted clauses or repetition.

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?

For a one-parameter read tool with full schema coverage and complete annotations, the description covers purpose, the ID source, and the shape of the return value well enough to call it correctly. Only minor gaps remain, such as handling of an invalid ID.

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% and the single parameter is already documented in the schema, so the schema does the work. The description only repeats the provenance of lesson_id ('from find_pain_lessons') without adding format or constraint details, which matches the baseline for a fully documented 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?

The description states a specific verb and resource ('Returns the content and key takeaways of one Recalibrate Academy lesson') and scopes it to a single lesson. It implicitly separates itself from find_pain_lessons by framing that tool as the source of the ID, though it never states the contrast explicitly.

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 one concrete usage condition: the lesson_id must come from find_pain_lessons, and the phrase 'so it can be taught in the conversation' hints at the intent. There is no explicit guidance on when not to use it or what to do if the ID is unknown/invalid.

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