Skip to main content
Glama

nexo_change_log

Log code or configuration changes with full context, including what changed, why, trigger, affected systems, and risks.

Instructions

Log a code/config change with full context: what, why, trigger, affects, risks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesFile path(s) modified (comma-separated if multiple)
what_changedYesWhat was modified — functions, lines, behavior change
whyYesWHY this change was needed — the root cause, not just "fix bug"
triggered_byNoWhat triggered this — bug report, metric, user's request, followup ID
affectsNoWhat systems/users/flows this change impacts
risksNoWhat could go wrong — regressions, edge cases, dependencies
verifyNoHow to verify this works — what to check, followup ID if created
commit_refNoGit commit hash (can be added later with nexo_change_commit)
session_idNoCurrent session ID
Behavior3/5

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

No annotations provided; description discloses the action and context but does not mention behavioral details like destructiveness, permissions, or side effects.

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?

Single sentence, front-loaded with action and key context fields. No wasted words.

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?

Covers high-level intent and lists context fields. No output schema exists, but description does not explain return behavior. Adequate for a logging tool.

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 100% with detailed parameter descriptions. The tool description adds no new meaning beyond what the schema already provides.

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 'Log' and specific resource 'code/config change', and lists the context fields. It distinguishes from sibling tools like nexo_change_commit and nexo_change_search.

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?

The description implies usage for logging changes with full context but lacks explicit guidance on when to use this tool vs alternatives like nexo_change_commit.

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