Skip to main content
Glama
Sign In
Kratos-MCP

Kratos-MCP

by FoggyStorm
OverviewSchemaRelated ServersDiscussionsAdmin
TypeScript
Hybrid

system_migrate

Migrate from legacy JSON to SQLite format on Kratos-MCP. Supports dry runs, backups, and concept extraction for AI coding tools to enhance memory and codebase context management.

Instructions

Migrate from legacy JSON format to SQLite

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": "system_migrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
create_backupNoCreate backup before migration
dry_runNoPerform dry run without changes
extract_conceptsNoExtract concepts during migration

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions migration but doesn't explain critical behaviors like whether this is a destructive operation, what permissions are needed, if it's reversible, or what happens to the original JSON data. For a migration tool with zero annotation coverage, this leaves significant gaps in understanding the tool's impact.

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 a single, efficient sentence that immediately conveys the core purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse while covering the essential action.

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

Completeness2/5

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

For a migration tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the migration entails, what systems are affected, success/failure conditions, or output format. Given the complexity implied by 'migrate' and the lack of structured behavioral data, more context is needed for the agent to use this tool effectively.

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%, so the schema already documents all three parameters (create_backup, dry_run, extract_concepts) with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema, which is acceptable but not exceptional given the comprehensive schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Migrate') and the resources involved ('from legacy JSON format to SQLite'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its siblings like 'system_status' or other system tools, which would be needed for a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context for migration. Given siblings like 'system_status' and various security tools, there's no indication of when migration is appropriate or how it relates to other system operations.

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

Related Tools