Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_migration_pilot

Analyze a codebase for breaking-change APIs ahead of a library or framework upgrade, and get a step-by-step migration checklist.

Instructions

Analyse a codebase for breaking-change APIs given a target library/framework upgrade. Returns a step-by-step migration checklist.

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": {
      "goal": "<goal>"
    },
    "name": "timps_migration_pilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYese.g. 'migrate from React 17 to React 18'
repo_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It mentions 'Analyse' and 'Returns a checklist', which suggests read-only behavior, but it doesn't explicitly state whether the tool modifies code, requires network access, or performs side effects. This lack of explicit transparency about side effects is a significant gap.

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?

The description is concise (two sentences) and well-structured, with no unnecessary detail. It efficiently conveys the core functionality and output.

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?

With no output schema, the description adequately explains the return value (step-by-step checklist) and the input factors (target upgrade, codebase). It lacks explicit mention of prerequisites or external interactions, but the core use case is covered sufficiently.

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?

Only 'goal' has a description with an example; 'repo_path' lacks a description. The tool's description mentions 'codebase', which gives some context for repo_path, but it's not fully specified. Schema coverage is partial at 50%, and the description adds moderate value.

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?

The description clearly states the tool's purpose: analyzing a codebase for breaking-change APIs in the context of a library/framework upgrade. It also specifies the output (step-by-step migration checklist), making it distinct from siblings like timps_db_migration_pilot.

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?

The description implies when to use it ('given a target library/framework upgrade') and what it does (identify breaking changes). It doesn't explicitly exclude alternative tools, but the scenario is clear enough.

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