Skip to main content
Glama

Read a Learn page

learn_read
Read-onlyIdempotent

The full text of one Learn article, glossary term, calculator page or research page by slug, as Markdown with its link. Use learn_search first when the slug is unknown.

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": {
      "slug": "<slug>"
    },
    "name": "learn_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe page slug or path, for example iron-condor-entry-screening or /learn/glossary/delta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / maxLength
      Added value: +160
    • addedInput schema / properties / slug / pattern
      Added value: +"^[A-Za-z0-9/_.#?=&-]+$"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds value beyond that by disclosing the return shape (Markdown text plus link). It does not say what happens when a slug is invalid or not found, which is the one behavioral gap.

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 with no wasted words: the capability and return format come first, followed by the routing rule. Nothing is buried or repeated from structured fields.

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?

For a single-parameter read tool with full schema coverage and rich annotations, the description covers what it returns and how to obtain a slug. No output schema exists, but the Markdown-plus-link return format is stated, so an agent has everything needed to call it 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 description coverage is 100% and the slug property already includes a pattern, length limit, and two concrete examples. The description's phrase 'by slug' adds nothing beyond the schema; the baseline of 3 applies when the schema carries the parameter documentation.

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 and resource — retrieves the full text of one Learn page by slug — and enumerates the content types covered (article, glossary term, calculator page, research page) plus the return format (Markdown with its link). It is clearly distinguishable from learn_search, which searches rather than reads.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use learn_search first when the slug is unknown.' This names the alternative sibling and the exact condition that selects it, so an agent knows both when to use this tool and when to use another first.

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