machinegrade-validate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SANDBOX_URL | No | The URL of the machinegrade validate server | http://localhost:8787 |
| SANDBOX_API_KEY | Yes | Your API key for the machinegrade validate server |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validateA | Validate an artifact against a contract (json_schema | openapi_response | sql) via the machinegrade validate API. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The single tool's purpose is clearly and uniquely defined.
The single tool name 'validate' is concise, follows a verb-action pattern expected for a validation server, and is fully consistent within the set.
Having only one tool feels thin for a server that could potentially offer multiple validation operations or contract management. While the tool covers the core validation task, the scope seems limited.
The tool comprehensively addresses the server's stated purpose of validating artifacts against contracts, supporting three common validation types (json_schema, openapi_response, sql) through a single API.