memory-bank-mcp

Overview Schema Source Related Servers Discussions Admin

migrate_file_naming

Migrate Memory Bank files from camelCase to kebab-case naming convention to ensure consistent file naming across your project context.

Instructions

Migrate Memory Bank files from camelCase to kebab-case naming convention

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Apr 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations exist, so the description must reveal behavior. It only states migration but does not explain what 'migrate' entails (e.g., renaming files, updating references, creating backups, reversibility, or safety). This lack of detail hinders the agent's understanding of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no filler. However, it could be slightly more informative without losing conciseness (e.g., mentioning it renames files).

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

Completeness3/5

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

Given no parameters, no output schema, and no annotations, the description captures the core purpose but leaves gaps about behavior, side effects, and prerequisites. For a tool with zero parameters, completeness is moderate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the description cannot add parameter-level semantics. The baseline for zero parameters is 4, and the description correctly summarizes the tool's action without needing to detail parameters.

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 explicitly states the action ('Migrate'), the resource ('Memory Bank files'), and the specific transformation ('from camelCase to kebab-case naming convention'). It clearly distinguishes from sibling tools, none of which mention naming migration.

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?

No guidance is provided on when to use this tool, prerequisites, or when not to use it. There is no mention of alternatives or required conditions (e.g., ensuring no concurrent file operations).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.