Skip to main content
Glama
Sign In
Asynthetic

Asynthetic

Official
by asyntheticai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check peer compatibility between two package versions

check_peer_compatibility
Read-only

Check compatibility of two package versions using curated peer dependency data from migration maps. Returns true, false, or unknown.

Instructions

Static SemVer check of two known package versions against curated compatible_with peer data from migration maps. Purely declarative — no filesystem access or project inspection (that is the scope of the separate, unimplemented check_compatibility). Returns compatible: true | false | "unknown". Treat "unknown" as absence of curated data, never as evidence of incompatibility.

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_a": "<package_a>",
      "version_a": "<version_a>",
      "package_b": "<package_b>",
      "version_b": "<version_b>"
    },
    "name": "check_peer_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemNoPackage ecosystem (default "npm")npm
package_aYesFirst package name, e.g. "next"
package_bYesSecond package name, e.g. "react"
version_aYesVersion (or SemVer range) of package_a, e.g. "15.0.0"
version_bYesVersion (or SemVer range) of package_b, e.g. "18.2.0"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Disclosure goes beyond annotations (readOnlyHint, openWorldHint) by clarifying no filesystem access, return types (true|false|'unknown'), and semantics of 'unknown'. No contradiction with annotations.

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 concise sentences with critical information front-loaded. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, no output schema, and sibling tools, the description fully explains purpose, behavior, parameter usage, and result interpretation. No gaps identified.

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 coverage is 100% with clear descriptions for all 5 parameters. Description adds no further semantic detail for parameters but provides examples and return value context, maintaining baseline adequacy.

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 explicit verb ('check') and resource ('peer compatibility between two package versions'), and distinguishes from sibling 'check_compatibility' by noting its different scope.

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

Usage Guidelines5/5

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

Explicitly states when to use (static SemVer check against curated data) and when not to (no filesystem access, contrast with unimplemented check_compatibility). Includes guidance on interpreting 'unknown' results.

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