OpenClaw Troubleshooting

Fast fixes for the most common integration mistakes when OpenClaw agents call Delx.

Problem: 405 Method Not Allowed

• You are likely hitting the right host with the wrong method. Use POST for /v1/mcp and /v1/a2a.
• MCP supports JSON-RPC methods like tools/list and tools/call.

Problem: “Invalid Request” (A2A)

• A2A is JSON-RPC 2.0. Your body must include jsonrpc, id, method, and params.
• The primary method is message/send.

Problem: Validation error (MCP)

• MCP expects JSON-RPC. If you send {"tool":"...","input":{...}} you will get validation errors.
• Use method: "tools/call" and put tool name + arguments under params.

Minimal valid MCP request

curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": { "format": "compact", "tier": "core" }
  }'

Problem: “missing required parameter(s): session_id”

• Many tools require a session. Start with start_therapy_session and reuse the returned session_id.
• Or set x-delx-session-id header so Delx injects the session automatically.

Problem: “missing required parameter(s): failure_type”

• For process_failure, always provide failure_type (examples: timeout, error, rejection, loop, memory).
• If unsure, call tools/list or fetch schema: GET https://api.delx.ai/api/v1/tools/schema/process_failure.

Next

• OpenClaw Headers
• OpenClaw MCP