Skip to main content
Glama
Sign In
mcp-server-demo

mcp-server-demo

by charley-forey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_mcp_server

Generates a complete MCP server directory from selected endpoints and automatically creates a public GitHub repository with the generated code.

Instructions

Step 5 of 6. Generate a complete MCP server directory from the selected endpoints.

Requires step 4 (select_endpoint_bundle). Uses stored validated_spec and selected_endpoints. output_dir: optional path where to create the project (e.g. ./output/projectsight-mcp). repo_name: optional suggested repo name for step 6; if omitted, derived from API title.

If scaffold succeeds, automatically proceeds to step 6: creates a new public GitHub repo, uploads the directory, and returns repo_url. Always a new repo, always public. Returns: output_dir, files_created, tool_count, repo_url (if upload succeeded), next_step_guidance.

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

Input Schema

NameRequiredDescriptionDefault
repo_nameNo
output_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool automatically proceeds to create a new public GitHub repo and returns key outputs like output_dir, files_created, tool_count, and repo_url. However, it doesn't mention whether existing directories are overwritten or any permission requirements.

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, with every sentence adding value. It front-loads the main action and prerequisites, then details parameters and post-invocation behavior. No filler or redundancy.

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 tool with 2 optional params and no output schema, the description covers prerequisites, parameters, and return values. It mentions outputs like files_created and tool_count but could provide more details on their exact meaning. Overall, it is sufficiently complete for its complexity.

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?

Schema coverage is 0%, so the description compensates by explaining both parameters: output_dir as an optional path and repo_name as an optional suggestion derived from the API title if omitted. This adds meaningful context beyond the schema's type definitions.

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 action: 'Generate a complete MCP server directory from the selected endpoints.' It specifies the resource (MCP server directory) and distinguishes from siblings like upload_to_github and propose_endpoint_bundles, which handle different steps.

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 explicitly says 'Requires step 4 (select_endpoint_bundle)' and explains that success triggers step 6 (GitHub repo creation). It provides clear context for when to use the tool but does not explicitly state when not to use it or list alternatives.

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