Tools Reference

Tools Reference

The MCP server exposes 9 tools. Your AI assistant picks them automatically from your prompt, but they are documented here in full so you can call them directly over HTTP or check exactly what your assistant is doing.

Every argument below goes in params.arguments of a tools/call request — see Calling the MCP directly over HTTP.

Tool summary

Documentation tools

list_endpoints

Lists every documented endpoint, grouped by integration and category.

{ "name": "list_endpoints", "arguments": { "integration": "reverse" } }

Returns the 19 reverse-integration entries:

get_endpoint

Returns the full structured spec for one endpoint: request parameters, response fields, status codes, signature scheme and authentication.

{ "name": "get_endpoint", "arguments": { "integration": "reverse", "name": "Wager" } }

Returns JSON — the endpoint’s method, path, category, summary, every documented parameter with its type and whether it is required, the success response shape, and the applicable status codes.

search_docs

Free-text search over endpoint names, summaries and categories.

{ "name": "search_docs", "arguments": { "query": "free round", "integration": "reverse" } }

Signature tools

Both signature tools implement the reverse scheme exactly as described in Signature Validation:

Signature = base64_encode(HMACSHA256(Path-And-Query, base64_decode(Access Key Value)))
Header    = Authorization: HMAC-SHA256 Signature={Signature}

Pass the Access Key Value as key — the tool performs the base64 decode for you.

sign_request

Computes the signature and returns the ready-to-send header.

{
  "name": "sign_request",
  "arguments": {
    "integration": "reverse",
    "pathAndQuery": "/groove?request=getbalance&gamesessionid=123&accountid=456",
    "key": "<your Access Key Value>"
  }
}

Result:

Authorization: HMAC-SHA256 Signature=<base64 signature>

verify_signature

The request checker: confirms a signature matches the request. Use it when a signature is being rejected and you need to know whether the fault is yours or the sender’s.

Result is valid, or invalid signature (401).

Code generation tools

generate_snippet

A single runnable example for one endpoint, with the signing or verification step shown explicitly.

{
  "name": "generate_snippet",
  "arguments": { "integration": "reverse", "name": "Wager", "language": "python" }
}

generate_integration

Generates a complete, startable project — not a snippet. You get the files of a working skeleton:

• A real /groove entry point wired for all 7 reverse transaction operations: getaccount, getbalance, wager, result, rollback, jackpot, wagerAndResult.
• Inbound Authorization HMAC verification, implemented against the documented scheme.
• The documented success responses and the full error catalogue — HTTP 200 with the status in the body, as this API specifies.
• One wallet seam per operation family: the small set of files you fill in with your own logic, routed per brand.

{ "name": "generate_integration", "arguments": { "integration": "reverse", "language": "go" } }

Returns a JSON list of files, each with a path, content, and an action:

That split means you can re-run generate_integration after a docs update to refresh the plumbing without losing your own code.

Server tools

list_tools

Returns every registered tool with its description and full JSON input schema. No arguments. Useful for confirming your client is talking to the server you expect.

get_server_info

Reports the server’s identity and the size of its loaded catalogue. No arguments.

Use it as a liveness check: a successful response means your token is valid and the server is serving.