Skip to main content
Glama

lessons

Read project-specific executor guidance and delete entries containing specified text to manage reusable notes for a project.

Instructions

Lessons the executor has for a project. remove_containing deletes those with that text.

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>"
    },
    "name": "lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYes
remove_containingNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

C2.7/5.0
Behavior3/5

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

Without annotations, the description discloses one key behavior: passing remove_containing deletes matching lessons. However, it does not clarify the default read-only behavior, whether deletion is permanent, or what happens when remove_containing is empty, leaving significant gaps for a tool with no safety hints.

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?

The definition is two short sentences with no wasted words, but it is under-specified for a tool with two parameters and no annotations. The structure could front-load a clearer action verb instead of a noun fragment.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (two parameters, no annotations, output schema present but unseen), the description is too sparse. It omits the primary action, project_path semantics, default behavior, and any indication of the return value or side effects beyond the single deletion note.

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 0%, so the description must compensate. It explains remove_containing as deleting lessons containing the given text, but does not explain the required project_path parameter or the default empty-string behavior of remove_containing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Lessons the executor has for a project' but uses a noun phrase instead of a clear verb, leaving the primary action (list? retrieve?) implicit. It distinguishes itself from the sibling 'lesson_add' only by omission, not by explicit differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives or prerequisites, and no context for when remove_containing should be supplied versus omitted. The only usage hint is the parameter behavior, not tool selection.

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