Loading ToolBench

Reading the current corpus…

vscode-schemaforge MCP server · F · ToolBench

vscode-schemaforge

github.com/Coding-Dev-Tools/vscode-schemaforge

Bidirectional schema converter — convert between SQL DDL, Prisma, Django, TypeORM, SQLAlchemy, Alembic, JSON Schema, GraphQL, EF Core, Scala case classes

2026-07-28+5 tools

26/100

Definition Quality37

Protocol Readiness0

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

SchemaForge is a VSCode extension, not an MCP server. The codebase shows no MCP protocol implementation, no tool registration via MCP, and no remote transport. Tools are VSCode commands (package.json contributes.commands), not MCP tools. Input schemas exist for 2 of 5 tools; 3 tools have empty input objects. Descriptions are present but generic (10-50 chars). No output schemas documented. This is fundamentally a VSCode plugin misclassified as an MCP server.

Tools (5)

schemaforge.convertread onlysource verified50/100

Convert Schema File...

schemaforge.detectread onlysource verified52/100

Detect Format

schemaforge.diffread onlysource verified27/100

Diff Two Schema Files

schemaforge.quickConvertread onlysource verified25/100

Quick Convert (Active Editor)

schemaforge.showPreviewread onlysource verified30/100

Show live schema preview panel with conversions to multiple formats

Issues (5)

CRITICALmcp-protocol ↗

Not an MCP server. This is a VSCode extension with command-based tools, not an MCP-compliant tool server. No MCP protocol transport, no tool registration via MCP SDK, no remote accessibility.

schemaforge.convertschemaforge.quickConvertschemaforge.diffschemaforge.detectschemaforge.showPreview

CRITICALtool ↗

Three tools (quickConvert, diff, showPreview) have empty input schemas ({}). These tools cannot be invoked by agents without parameter guidance.

schemaforge.quickConvertschemaforge.diffschemaforge.showPreview

HIGHtool-description ↗

Descriptions are too short (10-50 chars). Rubric baseline is 194 chars average; descriptions under 20 chars score 0-20. 'Quick Convert (Active Editor)' and 'Diff Two Schema Files' lack context on when to use them, what they return, or prerequisites.

schemaforge.quickConvertschemaforge.diff

Recommendations

Migrate from VSCode extension architecture to a proper MCP server using the MCP SDK (Node.js or Python). Expose tools via MCP protocol with HTTP or STDIO transport.
Add complete input schemas to all 5 tools. quickConvert, diff, and showPreview currently have empty {} inputs, define required/optional parameters with types and descriptions.
Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and WHAT it returns. Example: 'Convert a schema file between formats (SQL, Prisma, GraphQL, etc.). Use when you have a source schema and need it in a different ORM or language. Returns the converted schema as a string.'
Document output schemas for all tools. Specify the structure of returned data (e.g., { converted_schema: string, source_format: string, target_format: string, warnings?: string[] }).
Add error handling guidance to tool descriptions. E.g., 'If the CLI is not found, install via: pip install schemaforge. If conversion fails, check that the input format is valid.'

Score history

Overall score trend

First recorded score · v2 rubric

26/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	26	2026-07-28+	v2