Skip to main content
Glama

lesson_add

Teaches the executor a standing rule for a project or all projects, so it applies instructions like language or style constraints before every task.

Instructions

Teach the executor a standing rule for a project (or for every project with project_path '*'). Example: 'Comments in English, no em dashes.' The executor reads its lessons before each task.

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": {
      "project_path": "<project_path>",
      "text": "<text>"
    },
    "name": "lesson_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
project_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that lessons persist and are read by the executor before each task, but says nothing about deduplication, replacement/overwrite semantics, or permissions — meaningful gaps for a mutation tool.

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?

Three concise sentences delivering purpose, example, and lifecycle effect in that order. Every sentence adds information with no padding.

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?

An output schema exists, so return values need not be described. For a two-parameter tool the description covers purpose, scope, example, and effect well; only deduplication/replace behavior and path format remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does explain that project_path '*' means every project and illustrates `text` content, but leaves project_path format ambiguous (filesystem path vs. project name) and says nothing about text constraints.

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 ('Teach the executor a standing rule for a project') and adds the wildcard scope for all projects. An agent can distinguish this add-style tool from the `lessons` sibling which presumably lists them.

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?

Gives a concrete usage scenario with an example rule and clarifies the '*' scope. It does not explicitly name the alternative (e.g., `lessons` to check existing rules) or state when not to use it, so it falls short of 5.

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