Manage Bet Codes

View Bet Slip (JSON & Text)

mbc_view_slip

Read-onlyIdempotent

Load a booking code on a bookmaker and return all games, markets, outcomes, odds, live scores, kickoff times, and total odds. Costs 1 credit after a successful read; failed lookups 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>",
      "bookmaker": "<bookmaker>"
    },
    "name": "mbc_view_slip"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	Booking code (e.g. '7B9A2F').
`bookmaker`	Yes	Bookmaker key or alias (e.g. 'sportybet', 'bet9ja', '1xng', 'msport').

Output Schema

Name	Required	Description	Default
`code`	No
`status`	No
`billing`	No
`bookmaker`	No
`selections`	No
`total_odds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the credit cost model and the fact that failures are not charged, which materially affects retry and error-handling decisions.

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

Conciseness5/5

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

Two sentences, zero filler, with the output payload listed first and the cost caveat second. Nothing can be trimmed without losing information.

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?

An output schema exists and annotations cover safety, so the description need not explain return values, and it correctly stays brief for a two-parameter read tool. Minor gaps remain around error behavior for invalid or expired booking codes, which the credit-cost sentence only partially addresses.

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% with both parameters documented and examples given ('7B9A2F', 'sportybet'), so the baseline of 3 applies. The description adds no additional semantics such as case sensitivity, alias resolution, or what happens with an invalid or expired code.

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

Purpose4/5

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

States a specific verb and resource ('Load a booking code on a bookmaker') and enumerates exactly what comes back (games, markets, outcomes, odds, live scores, kickoff times, total odds). It never explicitly distinguishes itself from the sibling mbc_view_slip_image, which is the nearest alternative, so it falls short of the 5 bar.

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

Usage Guidelines3/5

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

Usage is implied by the mechanics: you have a booking code and a bookmaker, so you load it. There is no statement of when to prefer this over mbc_view_slip_image or mbc_convert_code, and no exclusions or prerequisites for the two required inputs.

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?