A
license-
qualityC
maintenanceDeterministic JSON validation and repair for AI agents. Validates, repairs, schema-checks, and diffs JSON so long-running agents don't corrupt their session state with malformed writes.
MIT
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
- 1
- Server Listing
- machinegrade-validate
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsA
Average 3.6/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
There is only one tool, so there is no possibility of confusing it with others. The tool's purpose is clear and singular.
Naming Consistency5/5
With a single tool named 'validate', the naming is consistent and follows a simple verb format. There are no mixed conventions to cause confusion.
Tool Count2/5
The server has only one tool, which feels too few for any meaningful scope. Even for a narrow validation purpose, this is excessively minimal and likely to miss common requirements.
Completeness4/5
The tool covers the core validation action, supporting multiple contract types. However, it lacks ancillary operations such as batch validation, schema management, or result history, which are minor gaps for the stated purpose.
Available Tools
1 toolvalidateAInspect
Validate an artifact against a contract (json_schema | openapi_response | sql) via the machinegrade validate API.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Which validator to run. | |
| artifact | Yes | The artifact to validate, as a JSON value — not a JSON-encoded string. json_schema/openapi_response: the object/array/value itself. sql: the SQL statement as a string. | |
| contract | No | Validator-specific contract. json_schema: { schema }. openapi_response: { spec, path, method, status }. sql: { dialect }. |
Tool Definition Quality
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'validate' which implies a non-mutating check, but it does not describe return format, error behavior, or whether the operation is read-only. Key behavioral context is missing.
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 a single sentence that front-loads the core action and supported contract types. 'Via the machinegrade validate API' is slightly redundant but does not add significant noise. It is concise and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has nested objects, no output schema, and no annotations, the description is insufficient. It does not explain what the validation response looks like, how to interpret results, or any error conditions, leaving the agent with significant ambiguity about expected outputs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% — all three parameters (type, artifact, contract) are described in detail. The description adds no additional parameter meaning beyond the enum values in the schema, so a baseline score of 3 is appropriate.
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 purpose: 'Validate an artifact against a contract' and enumerates the supported contract types (json_schema | openapi_response | sql). This gives a specific verb, resource, and scope, making it obvious what the tool does.
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 implies when to use this tool by listing the three validator types, providing clear context for common validation scenarios. However, it does not explicitly mention alternatives or exclusions, as no sibling tools are present.
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!
Related MCP Servers
- Flicense-qualityBmaintenanceMonitor AI output schemas and API contracts for breaking changes — validate LLM JSON responses against defined schemas on a schedule
- AlicenseAqualityAmaintenanceValidates AI-generated Python: syntax, lint, security scan and deterministic repair.83MIT
- FlicenseBqualityDmaintenanceValidates schema files against customizable lint rules using Claude or Gemini AI, supporting JSON and SQL schemas with rules for naming, structure, and migration safety.1
Try in Browser
Your Connectors
Sign in to create a connector for this server.