Skip to main content
Glama
Sign In
@4da/mcp-server

@4da/mcp-server

Official
by 4DA-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Upgrade impact

upgrade_impact
Read-only

Check what changes before bumping a dependency: breaking changes, deprecations, security fixes, changelogs, and affected project files. Use it to plan safer upgrades.

Instructions

What changes between the installed version of ONE dependency and a target: changelog per release, breaking changes, deprecations, security fixes, and this project's files that import it. Call before upgrading or bumping a dependency.

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>"
    },
    "name": "upgrade_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYesPackage name exactly as published (npm: `zod`, `@scope/pkg`; crates.io: `fastembed`; PyPI: the distribution, `PyYAML`; Go: the module path, `github.com/jackc/pgx/v5`).
ecosystemNoRegistry. Default: inferred from the project's dependencies (required when the name exists in more than one).
to_versionNoTarget version. Default: the highest stable version on the registry.
from_versionNoCurrent version. Default: the version this project's lockfile resolves.
response_formatNoconcise (default): every breaking/deprecation/security entry plus up to 3 others per version. detailed: all entries, capped at 400.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv6.0.3
    • changedInput schema / properties / ecosystem / description
      Previous value: -"Registry. Default: inferred from the project's dependencies (required when the name exists in both)."New value: +"Registry. Default: inferred from the project's dependencies (required when the name exists in more than one)."
    • changedInput schema / properties / ecosystem / enum
      Previous value: -[
-  "npm",
-  "crates.io"
-]New value: +[
+  "npm",
+  "crates.io",
+  "PyPI",
+  "Go"
+]
    • changedInput schema / properties / package / description
      Previous value: -"Package name exactly as published (npm: `zod`, `@scope/pkg`; crates.io: `fastembed`)."New value: +"Package name exactly as published (npm: `zod`, `@scope/pkg`; crates.io: `fastembed`; PyPI: the distribution, `PyYAML`; Go: the module path, `github.com/jackc/pgx/v5`)."
  2. First observedv6.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-registry profile is covered. The description adds the multi-source nature of the result (changelog plus project-local import scan), which is useful. It does not, however, disclose cost, latency, or rate-limit behavior despite hitting a registry and indexing the codebase.

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 scope and the exact output contents, then the call trigger. No filler and nothing redundant with the schema.

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?

For a read-only, open-world tool with a fully described five-parameter schema and no output schema, this covers what the tool returns and when to invoke it. A small gap remains around cost/latency and how the from_version/to_version defaults interact when the lockfile is absent.

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%: every parameter including the package-name format conventions, the ecosystem enum, the version defaults, and the concise/detailed response format is documented in the schema. The description adds no semantics beyond that, so the baseline 3 applies.

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?

States a specific verb (report what changes) on a specific resource (one dependency between installed and target version) and enumerates the exact payload: changelog per release, breaking changes, deprecations, security fixes, and the project's own importing files. That enumeration distinguishes it from siblings like dependency_check and upgrade_planner.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: 'Call before upgrading or bumping a dependency.' That is clear context, but it names no alternative, so an agent cannot tell from this text whether upgrade_planner or vulnerability_scan is the better fit for a given situation.

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

Deploy Server

Other Tools