validate
Server Details
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- machinegrade/validate
- GitHub Stars
- 0
- Server Listing
- machinegrade-validate
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, naming is trivially consistent.
One tool is on the lower end of appropriate; it's functional but feels minimal for a validation server that could benefit from separate tools for different contract types.
The single tool covers major validation types (json_schema, openapi_response, sql), leaving only minor gaps for other potential contract formats.
Available Tools
1 toolvalidateBInspect
Validate an artifact against a contract (json_schema | openapi_response | sql) via the machinegrade validate API.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Which validator to run. | |
| artifact | Yes | The artifact to validate (object for json_schema/openapi_response, SQL string for sql). | |
| contract | No | Validator-specific contract. json_schema: { schema }. openapi_response: { spec, path, method, status }. sql: { dialect }. |
Tool Definition Quality
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 mentions 'via the machinegrade validate API' but does not disclose whether the operation is read-only, synchronous, or has side effects. A validation tool likely does not mutate state, but this is not stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence. Every part earns its place: verb, resource, types, and API. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description should explain return values (e.g., validation result structure) and error cases. It fails to do so, leaving the agent without critical context for interpreting outcomes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds a general context of validating artifacts against a contract but does not provide additional meaning beyond the schema's parameter descriptions. The enumeration of types in the description loosely mirrors the schema's enum.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'validate' and resource 'artifact against a contract' with explicit type options in parentheses. With no sibling tools, differentiation is not needed, making this a clear statement of purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Although there are no sibling tools requiring when-not guidance, the description provides no usage context such as prerequisites or when to choose each validation type. It is minimally adequate but lacks explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.