rest_design_endpoints
Design RESTful API endpoints by defining resource names, HTTP methods, and status codes to ensure proper API structure.
Instructions
Design RESTful API endpoints with proper resource naming, HTTP methods, and status codes
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": {
"resource_name": "<resource_name>"
},
"name": "rest_design_endpoints"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actions | No | Custom actions beyond CRUD (e.g. 'activate', 'archive') | |
| api_key | No | API key for authentication | |
| resource_name | Yes | The primary resource name (e.g. 'users', 'orders') | |
| nested_resources | No | Optional nested/sub-resources |