Skip to main content
Glama
Sign In
Project Brain

Project Brain

by Perlitten
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Record a task lesson

record_task_lesson
Idempotent

Capture task-owned reported evidence as L1 lessons for Project Brain; L3 changes require human approval.

Instructions

Capture task-owned reported evidence as L1; L3 still needs human approval.

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": {
      "task_id": "<task_id>",
      "statement": "<statement>",
      "category": "<category>",
      "validation_id": "<validation_id>",
      "artifact_ids": "<artifact_ids>",
      "source_refs": "<source_refs>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "record_task_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
categoryYes
statementYes
source_refsYes
artifact_idsYes
validation_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.2

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already establish this is a non-destructive, idempotent write, so the safety profile is covered. The description does hint at a tiered evidence model (L1 auto-captured vs L3 requiring human approval), which is real context beyond the annotations, but it never explains what those tiers mean or what the idempotency_key and validation_id do.

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?

A single short clause with no filler and the core action front-loaded. It is appropriately sized in form, though that brevity stems partly from saying almost nothing.

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

Completeness1/5

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

For a 7-required-parameter evidence-recording tool with no output schema and only minimal annotations, the description is far too thin. It omits parameter meanings, the L1/L3 taxonomy, idempotency semantics, and any notion of what constitutes a valid lesson or how the referenced artifacts/validation are resolved.

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

Parameters1/5

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

All 7 parameters are required with 0% schema description coverage, and the description supplies no meaning for any of them — not task_id, category, statement, artifact_ids, validation_id, source_refs, or idempotency_key. With zero structured coverage, the description was the only place to compensate and it does nothing.

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

Purpose2/5

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

The verb 'capture' plus 'task-owned reported evidence' gestures at a write action, but the object is opaque: 'L1' and 'L3' are undefined jargon, and nothing distinguishes this from siblings like record_task_observation or record_procedure_outcome. An agent cannot tell what a 'task lesson' actually is.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite several closely related record_* tools. The clause about L3 needing human approval implies a workflow boundary but never states the condition for choosing this tool.

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

Deploy Server

Other Tools