Skip to main content
Glama
wazionapps

NEXO Brain

by wazionapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nexo_learning_add

Add a new learning entry to document resolved errors, patterns, or gotchas. Provide context, solution, and optional reasoning to prevent recurrence.

Instructions

Add a new learning (resolved error, pattern, gotcha).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort title for the learning.
contentYesFull description with context and solution.
categoryYesFree-form category name (e.g., 'backend', 'frontend', 'devops', 'infrastructure', 'security'). Use consistent names across learnings.
priorityNocritical, high, medium, low (default: medium). Critical/high never decay below floor.medium
reasoningNoWHY this matters — what led to discovering this (optional).
applies_toNoFiles, systems, or areas this learning applies to (optional).
preventionNoConcrete rule/check that prevents repeating this mistake (optional).
review_daysNoDays until this learning should be reviewed again (default 30).
supersedes_idNoExisting learning ID this new canonical rule replaces (optional).
source_authorityNoAuthority tier for conflict resolution: francisco_correction, explicit_instruction, code_test_evidence, deep_sleep, inference.explicit_instruction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv7.37.4
  2. Removedv7.23.8
  3. Addedv7.20.23
  4. Removedv7.20.14
  5. Addedv7.17.4
  6. Removedv7.17.1
  7. Changed10 schema fields changedv7.13.7
    • addedInput schema / properties / applies_to
      Added value: +{
+  "default": "",
+  "description": "Files, systems, or areas this learning applies to (optional).",
+  "type": "string"
+}
    • addedInput schema / properties / category / description
      Added value: +"Free-form category name (e.g., 'backend', 'frontend', 'devops', 'infrastructure', 'security'). Use consistent names across learnings."
    • addedInput schema / properties / content / description
      Added value: +"Full description with context and solution."
    • addedInput schema / properties / prevention
      Added value: +{
+  "default": "",
+  "description": "Concrete rule/check that prevents repeating this mistake (optional).",
+  "type": "string"
+}
    • addedInput schema / properties / priority
      Added value: +{
+  "default": "medium",
+  "description": "critical, high, medium, low (default: medium). Critical/high never decay below floor.",
+  "type": "string"
+}
    • addedInput schema / properties / reasoning / description
      Added value: +"WHY this matters — what led to discovering this (optional)."
    • addedInput schema / properties / review_days
      Added value: +{
+  "default": 30,
+  "description": "Days until this learning should be reviewed again (default 30).",
+  "type": "integer"
+}
    • addedInput schema / properties / supersedes_id
      Added value: +{
+  "default": 0,
+  "description": "Existing learning ID this new canonical rule replaces (optional).",
+  "type": "integer"
+}
    • addedInput schema / properties / title / description
      Added value: +"Short title for the learning."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  8. First observed

TDQS

C2.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only says 'Add a new learning' with no information on idempotency, side effects (e.g., does it trigger retroactive application?), conflict handling, auth requirements, or rate limits. This is severely lacking 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no unnecessary words. However, it lacks structure (e.g., no bullet points or clear breakdown) and could be slightly more informative without becoming verbose. It earns its place but could be improved.

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 has 10 parameters, full schema documentation, and no output schema, the description is too brief. It does not mention what the tool returns (e.g., the ID of the created learning), any confirmation, or how the 'supersedes_id' or 'source_authority' parameters affect behavior. The description is insufficient for complete understanding.

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%, with all 10 parameters having detailed descriptions in the input schema. The tool description adds no additional meaning beyond what schema provides (e.g., the parenthetical 'resolved error, pattern, gotcha' is implicit from the name and schema). Baseline of 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the tool's purpose: 'Add a new learning (resolved error, pattern, gotcha).' It uses a specific verb ('Add') and resource ('learning'), and differentiates from sibling tools like nexo_learning_update, nexo_learning_delete, and nexo_learning_list by focusing on creation.

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?

The description provides no guidance on when to use this tool versus alternatives. Among many sibling learning tools (e.g., nexo_learning_update, nexo_learning_search, nexo_learning_delete), there is no context for when to choose 'add' over other operations, nor any prerequisites or exclusions.

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