schema-sieve-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCHEMA_SIEVE_ROOT | No | Root directory that bounds file access. Defaults to the workspace parent when launched from the package. | workspace parent |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_schemaA | Summarize a local JSON Schema's types, properties, required fields, composition, and constraints without returning examples or defaults. |
| plan_fixtureA | Create a privacy-safe placeholder plan for test fixture fields in a local JSON Schema. It does not fabricate or copy example data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: inspect_schema provides a summary/description of the schema, while plan_fixture creates a placeholder plan for test fields. There is no overlap in their responsibilities.
Both tool names follow a consistent verb_noun pattern (inspect_schema, plan_fixture), using the same underscore style and analogous structure. The naming is predictable and coherent.
With only two tools, the set is on the thin side. While each tool serves a distinct purpose and fits a narrow domain, the count is at the lower boundary of what is typically considered well-scoped.
The tools cover the core workflow of inspecting a schema and planning fixtures without exposing example data. Minor gaps exist, such as a tool to validate or compare schemas, but the two tools together provide a coherent, non-redundant surface for the stated purpose.