Manage Bet Codes

Convert One Bet Code to All Bookmakers

mbc_convert_to_all

Convert one booking code to ALL supported target bookmakers at once (up to 27 target bookmakers: SportyBet, 1xBet Global, 1xBet NG, MSport, Paripesa, 22Bet, Megapari, 888starz, Afropari NG, Afropari Global, Betwinner, Melbet, Helabet, Fastpari, Xparibet, Goldpari, 1xBit, WinWinBet, DBBet, Paripulse, BetJam, Planbet, Linebet, Luckypari, Bet9ja, BetKing, Football.com), or pass a custom targets subset. Uses per-family concurrency lanes. Costs 2 credits per successful target code; failed targets cost 0 credits.

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": {
      "code": "<code>",
      "from_bookmaker": "<from_bookmaker>"
    },
    "name": "mbc_convert_to_all"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Source booking code (e.g. '7B9A2F').
`targets`	No	Optional list of target bookmaker keys. Omit to convert to all eligible bookmakers.
`include_card`	No	Set true to also render a 1080x1920 PNG share card with all converted codes.
`from_bookmaker`	Yes	Source bookmaker key or alias (e.g. 'sportybet', 'bet9ja').

Output Schema

Name	Required	Description	Default
`pairs`	No
`slips`	No
`billing`	No
`success`	No
`successful_pairs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only say the call is open-world, non-idempotent, and non-destructive. The description adds the decisive behavioral facts: a hard 27-target ceiling, per-family concurrency lanes, and a precise cost model where a successful target costs 2 credits and failures cost 0 — critical for a non-idempotent paid operation the agent may retry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then the target enumeration, then cost/concurrency behavior. The 27-name list is long but earns its place as the only enum documentation; the paragraph could be split into separate sentences for scannability, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, paid, fan-out conversion tool with an output schema already describing results, the description covers scope, limits, cost, and the optional share card. The only unaddressed edge is partial-failure semantics (what the response looks like when some targets fail), which the output schema can carry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: since the schema defines no enums for the targets array, the inlined list of 27 valid bookmaker keys is the only source of allowable values. It also clarifies that omitting 'targets' means all eligible bookmakers rather than a default subset.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: convert ONE booking code to ALL supported bookmakers at once, capped at 27, with the full bookmaker list inlined. The 'ALL ... at once' framing and the 'or pass a custom targets subset' clause clearly separate it from a single-target convert tool, so an agent can route without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit mode selection: omit 'targets' to convert to every eligible bookmaker, or supply a subset to narrow. It stops short of naming a sibling (e.g. single-target convert or bulk convert) and stating when that alternative is preferable, so the agent must infer the boundary from the 'ALL' scope word.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Manage Bet Codes tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?