agent-validator-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_api_endpointA | Test a single API endpoint for agent accessibility. Checks response format, status codes, documentation quality, and gives a score from 0-100. Args: url: The API endpoint URL to test method: HTTP method (GET, POST, etc.) expected_format: Expected response format (json, xml, text) |
| validate_openapi_specA | Validate an OpenAPI spec for agent-friendliness. Checks if the API documentation is good enough for AI agents to use the API effectively. Args: spec_url: URL to OpenAPI/Swagger spec |
| check_agent_interface_urlA | Check if a domain hosts an Agent Interface spec. Looks for the spec at the well-known URL: https://domain/.well-known/agent-interface.json Args: domain: Domain to check (e.g. "example.com") |
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 3 tools
Each tool targets a distinct aspect of agent validation: checking a well-known URL, testing an API endpoint, and validating an OpenAPI spec. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case ('check_agent_interface_url', 'validate_api_endpoint', 'validate_openapi_spec'). The verbs differ appropriately for the actions.
Three tools are appropriate for the focused domain of agent validation. They cover the essential validation tasks without being excessive or insufficient.
The set provides a complete surface for agent validation: domain-level interface detection, endpoint testing, and spec analysis. No obvious gaps exist for the stated purpose.