Manage Bet Codes

Convert Bet Code (1 to 6 Targets)

mbc_convert_code

Convert a booking code from one source bookmaker to 1 target bookmaker or a synchronous batch of up to 6 target bookmakers. Costs 2 credits per target that produces a code; failed targets are automatically refunded. To convert to all bookmakers at once (up to 27), use mbc_convert_to_all.

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>",
      "to_bookmakers": "<to_bookmakers>"
    },
    "name": "mbc_convert_code"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	Source booking code (e.g. '7B9A2F').
`to_bookmakers`	Yes	Target bookmaker key/alias or list of 1 to 6 targets (e.g. '1xng' or ['1xng', 'bet9ja', 'msport']).
`from_bookmaker`	Yes	Source bookmaker key or alias (e.g. 'sportybet', 'bet9ja', '1xng', 'stake').

Output Schema

Name	Required	Description	Default
`source`	No
`billing`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the pricing model (2 credits per successful target) and the refund policy for failed targets, plus that the batch is synchronous. Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). It does not note that repeat calls incur repeat charges despite idempotentHint=false.

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?

Three tight sentences, front-loaded with the core action and limits, with the cost model and alternative following in priority order. No filler, though the outline of the batch limit slightly repeats the schema's maxItems.

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

Completeness4/5

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

Covers purpose, limits, cost, and the sibling alternative, and an output schema exists so return values need not be explained. The main residual gap is that the non-idempotent, credit-charging nature of retries is not spelled out for an agent deciding whether to re-invoke.

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

Parameters3/5

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

Schema coverage is 100% and already documents all three parameters with examples and the maxItems of 6, so the schema does the heavy lifting. The description adds only the batch-size framing ('up to 6') and the synchronous-execution note, both of which are largely restated from the schema constraints.

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 the specific action ('Convert a booking code') with its resource and explicit limits (1 target or a synchronous batch of up to 6), and names the sibling tool that handles the wider case. An agent can distinguish it from mbc_convert_to_all without opening a 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?

Explicitly routes the agent: use mbc_convert_to_all for up to 27 bookmakers. That gives a clear when-to-use-this-vs-that condition, though it doesn't address other conversion siblings such as mbc_bulk_convert or mbc_merge_codes.

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?