inspect
Retrieve the full OpenAPI operation object for any endpoint — parameters, request body, response schemas, and definitions. Use to understand exact technical details before calling an endpoint via invoke.
Instructions
inspect
Retrieves the full OpenAPI operation object for an endpoint — parameters, request body, response schemas, and all definitions.
Use this when you need complete technical details before invoking an endpoint or explaining its contract to the user.
For a quick summary (method, path, summary only), use endpoint_by_id instead.
When to use
Use this tool when:
The user asks "show me the full spec for this endpoint"
You need to understand the exact schema for request/response bodies
You need to know which parameters (path, query, header) an endpoint accepts
You are preparing to call an endpoint via
invokeand need to build the correct requestThe user asks for examples, response codes, or technical contract details
Parameters
endpointId(required): The 32-character MD5 hash ID of the endpoint to inspect
Returns
The full OpenAPI operation object including parameters (with schemas), request body, responses, and all referenced schema definitions.
Note on auth-injected parameters
Some required parameters shown by inspect may be auth credentials (e.g. api_key, timestamp, signature, recvWindow). These are injected automatically by swag2mcp during invoke — do NOT pass them in parameters. Only pass genuine business parameters.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| endpointId | Yes | required,The 32-character MD5 hash ID of the endpoint to inspect |