Upgrade Brief

by dev.workers.shopttyass-85f.upgrade-brief

npm changelog

npm_changelog

Read-onlyIdempotent

npm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.json changes. Paid: $0.01 USDC per call via x402.

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": {
      "package": "<package>",
      "from": "<from>"
    },
    "name": "npm_changelog"
  }
}

Input Schema

Name	Required	Description
`to`	No	Target version: exact, or a major/minor prefix ('19', '2.0') meaning the first release of that series (19.0.0). Default: latest stable
`from`	Yes	Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21') meaning the newest release of that series
`package`	Yes	npm package name, e.g. 'react', 'next', '@types/node'
`maxVersions`	No	Newest N versions to return notes for (default 30)
`prereleases`	No	Include alpha/beta/rc versions in the range

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantial context beyond them: output ordering (newest first), the exact contents of each entry, and critically the paid pricing model ($0.01 USDC per call via x402). The pricing disclosure is a required behavioral trait an agent must know before calling and is absent from structured fields.

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?

Two sentences, front-loaded with the core purpose and output shape, followed by the pricing constraint. No wasted words; every clause carries information.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their ordering, so an agent knows what to expect. Pricing is disclosed. The only minor gap is guidance on the array result size relative to maxVersions, which is left to the schema.

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 from/to/to/package/maxVersions/prereleases are already fully documented in the schema. The description reinforces the 'range between two versions' framing but adds no syntax or defaults beyond what the schema provides. Baseline 3 is 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?

Specific verb+resource: 'npm changelog between two versions' with a precise enumeration of what the notes contain (dates, bump type, deprecations, breaking changes, package.json changes). It does not explicitly state how it differs from siblings like npm_breaking_changes or npm_versions, leaving that distinction implicit.

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 when it applies (getting a version range changelog) but never states when to prefer it over npm_breaking_changes or npm_versions, nor any prerequisites. Usage is inferable but not explicit.

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

All Upgrade Brief tools Inspect

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

Need Help?