Upgrade Brief

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

go breaking changes

go_breaking_changes

Read-onlyIdempotent

Go module upgrade brief between two versions: go.mod diff (go directive, requirements), major /vN import path change with the rewrite command, retracted and deprecated flags, breaking items from GitHub releases and CHANGELOG, the go get command. Paid: $0.005 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": {
      "module": "<module>",
      "from": "<from>"
    },
    "name": "go_breaking_changes"
  }
}

Input Schema

Name	Required	Description
`to`	No	Target version: exact, or a major prefix meaning its first release. Default: latest
`from`	Yes	Version you use now: exact or a major/minor prefix meaning its newest release
`module`	Yes	Go module path, e.g. 'github.com/gin-gonic/gin' (add /v2.. for v2+ modules)
`prereleases`	No	Include prerelease versions

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-schema information: it is a paid call at $0.005 USDC per call via x402, which materially affects invocation decisions. It does not cover failure behavior (unknown module, nonexistent version), which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that opens with what the tool returns and then lists the payload components; every clause carries content. The pricing clause is tucked at the end where it is easy to reach but it is not wasteful.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the brief's sections (diff, migration command, breaking items, go get command). Combined with the cost disclosure and 100%-documented schema, an agent has enough to call it correctly; only error behavior is missing.

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%, with each of module/from/to/prereleases documented including prefix semantics and defaults, so the baseline is 3. The description adds only the framing 'between two versions' and does not clarify version-prefix behavior or what 'to' defaulting to latest implies beyond the schema.

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?

The description concretely names the resource (Go module upgrade brief between two versions) and enumerates what the brief contains — go.mod diff, /vN import path change, retraction/deprecation flags, breaking items, go get command. The 'Go module' qualifier plus verbatim ecosystem specificity distinguishes it in practice from npm_breaking_changes, pypi_breaking_changes and the other ecosystem siblings, though it never explicitly says so.

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 by 'upgrade brief between two versions' — an agent can infer it is for upgrade planning. There is no explicit when-to-use/when-not framing and no named alternative such as dependency_upgrade_plan, which is arguably the closest competitor, so the agent must infer the boundary itself.

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?