Skip to main content
Glama
Sign In

Nitrozen

by io.nitrozen
OverviewDiscussionsAdmin

Update a changelog entry

update_entry
DestructiveIdempotent

Update a changelog entry's title, content, category, or publish status.

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_id": "<project_id>",
      "entry_id": "<entry_id>"
    },
    "name": "update_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title
contentNoNew content (Markdown)
categoryNoNew category slug. Every project has the built-in categories 'new', 'improvement', 'fix', and 'announcement'; projects with custom categories enabled may also have additional project-specific slugs.
entry_idYesEntry ID
project_idYesProject ID
is_publishedNoPublish or unpublish the entry
published_atNoISO 8601 publish date

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds no behavioral context. It does not explain partial-update behavior, whether omitted fields are preserved, or what destructive effect an update may have on existing content.

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?

A single, front-loaded sentence with no wasted words. It immediately communicates the operation and resource.

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

Completeness3/5

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

For a mutation tool with rich annotations and full schema coverage, the definition is minimally adequate. However, it omits partial-update semantics, publish-state behavior, and published_at from the field list, leaving gaps in how an agent should safely invoke it.

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 schema already documents all parameters including entry_id, project_id, and published_at. The description lists several fields but omits published_at and adds no syntax or semantics beyond the schema, making the baseline 3 appropriate.

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

Purpose4/5

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

States a specific verb (update) and resource (changelog entry) and names most editable fields. The purpose is unambiguous against siblings like create_entry, get_entry, and delete_entry, though it does not explicitly differentiate itself.

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?

Usage is implied: use this to modify an existing changelog entry rather than create or delete one. However, the description gives no explicit when-to-use conditions, prerequisites, or alternatives.

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

All Nitrozen toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources