Manage Bet Codes

Render Bet Slip Image (PNG)

mbc_view_slip_image

Read-onlyIdempotent

Render a branded PNG slip image for a booking code on a bookmaker. Returns an MCP ImageContent block (image/png) plus a summary. Costs 2 credits after a successful render; failed renders 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_image"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`code`	No
`bookmaker`	No
`mime_type`	No
`credits_charged`	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?

Goes meaningfully beyond the annotations by disclosing the return shape (MCP ImageContent block, image/png, plus a summary) and a precise cost model: 2 credits on successful render, 0 on failure. It does not cover permissions/auth or any rate limiting, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the action and resource, then return format, then cost. Every sentence carries information an agent needs before invoking the tool; nothing is padded.

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?

For a two-parameter read-only render tool with full schema coverage and an output schema, this covers action, return type, and billing behavior. The only gap is what happens on invalid codes or unknown bookmakers beyond the billing note.

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 description coverage is 100% and both parameters already carry inline descriptions with examples, so the schema does the heavy lifting. The description only restates that the code is a booking code and belongs to a bookmaker, adding no new syntax or format detail.

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: renders a branded PNG slip image for a booking code on a bookmaker. The image-rendering angle clearly distinguishes it from a plain data-view sibling, though it never names mbc_view_slip as the text alternative, so the differentiation must be inferred.

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 word 'Render' and the image output type, but there is no explicit when-to-use or when-not guidance, and no alternative is named. An agent can guess this is the tool for visual delivery versus textual data, but must do the work itself.

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?