Skip to main content
Glama
Sign In
Asynthetic

Asynthetic

Official
by asyntheticai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List available migration maps

list_available_maps
Read-only

List all available migration maps by ecosystem and package. Discover coverage for your library version upgrades before applying fixes.

Instructions

Lists every migration map in the store: package, ecosystem, from_version, to_version, status (draft/verified/stale), last_verified. Optional filters: ecosystem, package. Use this to discover coverage before calling get_migration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_available_maps"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoFilter by exact package name (case-insensitive)
ecosystemNoFilter by ecosystem, e.g. "npm"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds that the tool returns specific fields and supports filtering but does not discuss pagination or rate limits. Adequate but not extensive additional behavior beyond 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 tightly written sentences: the first defines output fields, the second specifies filters and usage context. No wasted words.

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 low-complexity tool (2 optional params, no output schema), the description covers the essential details: what is returned, optional filters, and its role relative to siblings. Could mention if results are paginated, but not critical for this case.

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 both parameters fully described in the JSON schema. The description restates the filter options but does not add new semantics beyond the schema.

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?

Clearly states it lists migration maps with specific fields (package, ecosystem, versions, status, last_verified) and optional filters. Distinguishes from siblings by positioning it as a discovery tool before calling get_migration.

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 explicit usage context: 'Use this to discover coverage before calling get_migration.' Does not detail when not to use, but the guidance is clear for a simple listing tool.

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