Skip to main content
Glama

nexo_learning_add

Capture a resolved error, pattern, or gotcha as a learning with title, category, and full context, and optionally set prevention rules and review schedule to avoid repetition.

Instructions

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

Input Schema

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

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like idempotency, return values, or side effects. It describes what the tool does, not how it behaves.

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 description is extremely concise (one sentence) but under-specified for a tool with 9 parameters. It lacks structure and front-loading of key constraints (e.g., required fields).

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?

Given the complexity (9 parameters, no output schema, no annotations), the description is severely incomplete. It omits return value information, fails to explain the significance of required vs optional fields, and provides no usage examples.

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%, so the description adds minimal value beyond listing field types (e.g., 'resolved error, pattern, gotcha' hints at content types but doesn't compensate for low coverage—actually coverage is high). Baseline 3 is appropriate.

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 verb 'Add' and the resource 'a new learning', with parenthetical types (resolved error, pattern, gotcha) that distinguish it from sibling tools like nexo_learning_update or nexo_learning_delete.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., nexo_learning_update for existing entries). The brief description implies creation, but lacks context about preferred use cases or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazionapps/nexo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server