Skip to main content
Glama
Sign In

Nitrozen

by io.nitrozen.mcp
OverviewDiscussionsAdmin

Get a changelog entry

get_entry
Read-onlyIdempotent

Get a single changelog entry by project and entry ID.

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": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYesEntry ID
project_idYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Since the annotations are highly descriptive (ReadOnlyHint: true, DestructiveHint: false, IdempotentHint: true), the description is not required to carry heavy behavioral weight. It provides minimal additional context on execution or constraints beyond the functional operation.

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?

The definition is extremely concise, consisting of a single, clear sentence that is fully front-loaded with the necessary action and scope.

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?

The description successfully conveys the functional intent and the specific method of retrieval. Given the strong annotations regarding safety and idempotency, the definition is complete for an agent to execute the tool correctly.

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?

The schema description coverage is 100%, providing a high baseline. The description merely restates the required parameters (project and entry ID) without adding any deeper semantic meaning to how they are formatted or validated beyond what the schema already dictates.

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 uses a specific verb ('Get') and clearly identifies the resource ('changelog entry') and the necessary parameters ('project and entry ID'). This is precise and effectively distinguishes it from sibling tools like list_entries.

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?

It clearly specifies the required inputs (both project and entry ID) for fetching a single item. However, it offers no explicit guidance contrasting when to use this over a list view sibling or why this specific retrieval method is preferred.

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