Skip to main content
Glama

AIML Rounds

Read a lesson

get_lesson
Read-only

Read one lesson as Markdown: the interview situation, intuition, how it works (with equations in TeX), in practice, and the model interview answer with follow-ups. Use an id from search (e.g. 'ai-engineering/prefill-vs-decode'), a page URL or a title. Use tab to read one part only.

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": {
      "id": "<id>"
    },
    "name": "get_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLesson id, URL or title
tabNoOptional: only this part, e.g. 'Intuition', 'How it works' / 'Maths', 'In practice', 'Say it' (the interview answer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint=false annotations already establish the safety profile, and the description adds the return format (Markdown) and the content shape of a lesson. It does not mention payload size, whether large lessons are truncated, or what happens when an id/title fails to resolve, which are the remaining behavioral gaps.

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?

The most valuable fact, the Markdown return and section list, is front-loaded, and the operational hints follow. It is a dense three-sentence block with almost no filler, though the section enumeration could be trimmed to a shorter list.

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 two-parameter read-only tool with no output schema and full schema coverage, the description supplies everything an agent needs: what is returned, its format, where ids come from, and how to limit output via tab.

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 parameters are already documented, including the tab examples. The description mostly restates the schema (id, URL, title; tab for one part) and only mildly extends it by pointing to search as the source of ids, so the baseline 3 applies.

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?

"Read one lesson as Markdown" gives a specific verb and a single, unambiguous resource, then enumerates the sections the lesson contains (situation, intuition, how it works, in practice, model answer). That level of detail lets an agent distinguish it from siblings like search or browse without opening the schema.

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?

It states the acceptable identifier sources (id from search, page URL, title) and gives a concrete id example, plus the condition for narrowing output ("Use tab to read one part only"). It stops short of explicitly naming a sibling trade-off (e.g. when to use search instead), so it is clear context without full exclusions.

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