rest_validate_conventions
Check REST API design against best practices and naming conventions. Submit an OpenAPI spec and select strictness level to catch violations and enforce consistent standards.
Instructions
Pro: Validate REST API design against best practices and naming conventions
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"openapi_spec": "<openapi_spec>"
},
"name": "rest_validate_conventions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | API key for authentication | |
| strictness | No | Validation strictness level | standard |
| openapi_spec | Yes | OpenAPI/Swagger spec or list of endpoints to validate |