Skip to main content
Glama
Sign In
MCP Server Generator

MCP Server Generator

by hitoshura25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

generate_claude_command

Create slash command files for Claude Code to guide users through MCP server development, from generation to implementation.

Instructions

Generate Claude Code command files for guided MCP development

Creates .claude/commands/ directory with slash command files that guide users through MCP server development using this generator.

Args: command_name: Name for the command (e.g., "mcp-generate", "mcp-help") command_type: Type of command to generate: - "mcp_generator": Guide through MCP server generation workflow - "best_practices": Provide MCP best practices reference - "implementation_helper": Help implement generated MCP server - "custom": Use custom_prompt for fully custom command description: Optional description for the command (auto-generated if not provided) custom_prompt: Required if command_type is "custom" output_dir: Directory to create command file (default: .claude/commands)

Returns: JSON string with generation result

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": {
      "command_name": "<command_name>"
    },
    "name": "generate_claude_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_nameYes
command_typeNomcp_generator
descriptionNo
custom_promptNo
output_dirNo.claude/commands

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description provides basic behavioral info: it creates the .claude/commands/ directory and files, and returns a JSON string. However, it omits details like whether existing files are overwritten, directory creation behavior, or permission requirements. Some transparency but not comprehensive.

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 well-structured with a clear purpose line followed by a brief overview and an Args section. It is appropriately sized for the complexity, though some sentences could be tightened. No unnecessary repetition.

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?

Given the moderate complexity (5 params, 1 required, enum) and the existence of an output schema, the description covers the main aspects: purpose, parameters, return type. It could be more complete with examples or error handling notes, but it is sufficient for basic usage.

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

Parameters5/5

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

The schema has 0% description coverage, so the description fully compensates by explaining each parameter in the Args section. It clarifies the command_type enum values, the optional nature of description, the requirement of custom_prompt for custom type, and the default output_dir. This adds significant meaning 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?

The description clearly states the tool's purpose as generating Claude Code command files for guided MCP development. It uses a specific verb (generate) and resource (Claude Code command files), and the purpose is distinct from sibling tools like generate_mcp_server or get_best_practices.

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 does not provide explicit guidance on when to use this tool versus its siblings. While it explains command types, it lacks statements like 'use this when you want to create slash commands' versus 'use generate_mcp_server for server creation.' No comparisons or exclusions are given.

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