Skip to main content
Glama

Get an AI PM Lab lesson

get_lesson
Read-onlyIdempotent

A lesson in full: the product decision it informs, its key idea and concepts, things to try with what to notice in each (from recorded runs), what a PM takes away and questions to ask engineers, with links to the lesson, its 3D tour and its challenge.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe lesson's slug, from search_lessons

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
      -  "how-llms-work",
      -  "writing-good-prompts",
      -  "hallucination-and-grounding",
      -  "embeddings-and-semantic-search",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "prompt-caching-and-cost",
      -  "structured-outputs",
      -  "how-ai-agents-work",
      -  "memory-and-long-conversations",
      -  "retrieval-augmented-generation",
      -  "tool-design-and-mcp",
      -  "multi-agent-systems",
      -  "workflows-vs-agents",
      -  "ai-evals",
      -  "reasoning-models",
      -  "production-monitoring",
      -  "prompt-injection",
      -  "model-routing",
      -  "human-in-the-loop",
      -  "spec-driven-development",
      -  "reviewing-ai-written-code",
      -  "letting-agents-edit-tests"
      -]New value: +[
      +  "how-llms-work",
      +  "writing-good-prompts",
      +  "hallucination-and-grounding",
      +  "embeddings-and-semantic-search",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "prompt-caching-and-cost",
      +  "structured-outputs",
      +  "how-ai-agents-work",
      +  "memory-and-long-conversations",
      +  "retrieval-augmented-generation",
      +  "tool-design-and-mcp",
      +  "multi-agent-systems",
      +  "workflows-vs-agents",
      +  "ai-evals",
      +  "reasoning-models",
      +  "production-monitoring",
      +  "prompt-injection",
      +  "model-routing",
      +  "human-in-the-loop",
      +  "spec-driven-development",
      +  "bug-report-is-the-prompt",
      +  "agent-rules-file",
      +  "reviewing-ai-written-code",
      +  "letting-agents-edit-tests",
      +  "coding-agent-permissions"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
      -  "how-llms-work",
      -  "writing-good-prompts",
      -  "hallucination-and-grounding",
      -  "embeddings-and-semantic-search",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "prompt-caching-and-cost",
      -  "structured-outputs",
      -  "how-ai-agents-work",
      -  "memory-and-long-conversations",
      -  "retrieval-augmented-generation",
      -  "tool-design-and-mcp",
      -  "multi-agent-systems",
      -  "workflows-vs-agents",
      -  "ai-evals",
      -  "reasoning-models",
      -  "production-monitoring",
      -  "prompt-injection",
      -  "model-routing",
      -  "human-in-the-loop"
      -]New value: +[
      +  "how-llms-work",
      +  "writing-good-prompts",
      +  "hallucination-and-grounding",
      +  "embeddings-and-semantic-search",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "prompt-caching-and-cost",
      +  "structured-outputs",
      +  "how-ai-agents-work",
      +  "memory-and-long-conversations",
      +  "retrieval-augmented-generation",
      +  "tool-design-and-mcp",
      +  "multi-agent-systems",
      +  "workflows-vs-agents",
      +  "ai-evals",
      +  "reasoning-models",
      +  "production-monitoring",
      +  "prompt-injection",
      +  "model-routing",
      +  "human-in-the-loop",
      +  "spec-driven-development",
      +  "reviewing-ai-written-code",
      +  "letting-agents-edit-tests"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
      -  "how-llms-work",
      -  "writing-good-prompts",
      -  "hallucination-and-grounding",
      -  "embeddings-and-semantic-search",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "prompt-caching-and-cost",
      -  "structured-outputs",
      -  "how-ai-agents-work",
      -  "retrieval-augmented-generation",
      -  "tool-design-and-mcp",
      -  "multi-agent-systems",
      -  "workflows-vs-agents",
      -  "ai-evals",
      -  "reasoning-models",
      -  "production-monitoring",
      -  "prompt-injection",
      -  "model-routing",
      -  "human-in-the-loop"
      -]New value: +[
      +  "how-llms-work",
      +  "writing-good-prompts",
      +  "hallucination-and-grounding",
      +  "embeddings-and-semantic-search",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "prompt-caching-and-cost",
      +  "structured-outputs",
      +  "how-ai-agents-work",
      +  "memory-and-long-conversations",
      +  "retrieval-augmented-generation",
      +  "tool-design-and-mcp",
      +  "multi-agent-systems",
      +  "workflows-vs-agents",
      +  "ai-evals",
      +  "reasoning-models",
      +  "production-monitoring",
      +  "prompt-injection",
      +  "model-routing",
      +  "human-in-the-loop"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "links": {
      +      "description": "The AI PM Lab pages the answer links to, where each idea can be tried hands-on",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "description": "The answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds useful context about what the returned content comprises (recorded-run observations, 3D tour, challenge links), but nothing about invalid-slug behavior or lookup failure.

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?

It is a single sentence front-loaded with 'A lesson in full', which is good, but it degenerates into a long colon-driven list whose clauses largely restate what the output schema already enumerates. It parses awkwardly and some items (3D tour, challenge) do little to help selection.

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, idempotent read tool with full annotations, a complete output schema and an enumerated slug, the definition supplies enough substance to call it correctly. The only real gap is the absent when-to-use framing, which is partly compensated by the schema's reference to search_lessons.

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 single slug parameter carries an enum of 25 valid values plus the note 'from search_lessons', so the schema fully documents it. The description adds nothing about the slug itself, so the baseline of 3 applies.

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 enumerates the concrete payload of a single lesson (decision, key idea, things to try, PM takeaway, questions, links), so an agent knows this returns full lesson content rather than a list. However it is a noun-phrase fragment with no explicit verb and no in-text differentiation from search_lessons, which is only supplied by the schema note 'from search_lessons'.

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?

There is no explicit statement of when to call this versus search_lessons or the other lesson-adjacent tools. Usage is only implied by the schema's 'from search_lessons' hint and by the phrase 'A lesson in full', which suggests a detail-fetch following a search. Workable but left to inference.

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