all scenarios

Duplicate tool names

duplicate-tool-names · Tools — listing

Endpoint (Streamable HTTP)
https://chaos-mcp.thomascdnns.com/s/duplicate-tool-names/mcp
On the wire — recorded from a real request
your clientchaos-mcp01initializePOST /s/duplicate-tool-names/mcp200 OK · application/json · 3 ms"jsonrpc""2.0""id"1"result""protocolVersion""2024-11-05""capabilities""tools""serverInfo""name""chaos-mcp/duplicate-tool-names""version""1.0.0""instructions""chaos-mcp scenario: duplicate-tool-names — Duplicate tool names"02tools/listPOST /s/duplicate-tool-names/mcp200 OK · application/json · 2 ms"jsonrpc""2.0""id"2"result""tools""name""search""description""Search the PRIMARY index.""inputSchema""type""object""properties""q""type""string""required"… 22 more lines

Symptom

what you'll observe

Two tools share a name; the client calls one but gets the other's behaviour.

Cause

what this reproduces

Name collision from merging tool sets or a templating bug.

Fix

how you'd resolve it

Enforce unique tool names at registration; namespace them if merging sources.

Try it with curl
bash
curl -sS -X POST \
  https://chaos-mcp.thomascdnns.com/s/duplicate-tool-names/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '
"jsonrpc""2.0"
"id"1
"method""initialize"
"params"
"protocolVersion""2024-11-05"
"capabilities"
"clientInfo""name""curl""version""1"

'