vdiff
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VDIFF_API_URL | No | Base URL of the vdiff API instance (defaults to the hosted https://vdiff-api.onrender.com). Leave unset to use the hosted service. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_packageA | Resolve an npm package to its latest published version and dist-tags. Use this when you only know the package name and need the current version, typically before calling get_breaking_changes. |
| get_breaking_changesA | Structured breaking-change diff between two versions of an npm package, computed from its TypeScript type declarations: removed exports, changed signatures, removed/changed class or interface members, plus new exports. Each entry has before/after signatures and a short migration note. The response includes a confidence score: 0.9 when both versions ship bundled types, 0.8 when DefinitelyTyped @types/* declarations were used. Use this before writing or upgrading code that targets a dependency version you are not certain about — e.g. when the installed version is newer than the API surface you know. The first request for a version pair may take up to a couple of minutes while the diff is computed; results are cached after that. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct purposes: one resolves package versions, the other computes breaking changes. There is no ambiguity or overlap.
Both tools follow a consistent verb_noun pattern with snake_case (resolve_package, get_breaking_changes), making them predictable.
With only two tools, the server is minimal but well-suited to its niche purpose of version analysis. It could benefit from additional utilities like listing versions, but the count is not inappropriate.
The tools cover the essential workflow: resolve a package name to a version, then get breaking changes. While there are no additional features like changelog retrieval or multi-package comparison, the core functionality is complete.