Skip to main content
Glama

Manage Bet Codes

Manage Bulk Jobs & Query Conversion / Book History

mbc_manage_jobs_and_history

Create, inspect, list, or cancel async jobs (for >6 targets or up to 20 source codes, requires Developer/Scale/Business API plan), or query past conversion history and book history (0 credits for reads).

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": {
      "action": "<action>"
    },
    "name": "mbc_manage_jobs_and_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
actionYesOperation to perform.
job_idNoJob ID 'job_...' for get_job or cancel_job.
offsetNo
row_idNoHistory ID ('hl_...') or Book ID for get_history or get_book.
statusNo
targetNo
bookmakerNo
job_payloadNoJob creation body for create_job: {kind: 'convert'|'split'|'merge'|'book', ...}.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds real value beyond that: the API-plan gate and the credit cost model (0 credits for reads). However, it never explains async job mechanics — whether create_job returns immediately and requires polling, what cancel_job does to partial output, or whether history reads are paginated — which is the behavior an agent most needs for a job tool.

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?

A single sentence, front-loaded with the action verbs and the job-versus-history split. Both parentheticals (plan requirement, credit cost) earn their place; the only cost is that cramming eight actions into one line makes the sentence dense to parse.

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

Completeness3/5

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

An output schema exists, so return values need not be described. But for a tool multiplexing eight actions over nine parameters, the description omits the action-to-parameter matrix and any async lifecycle detail, leaving an agent able to understand the tool's purpose but unsure how to invoke each action correctly.

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

Parameters2/5

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

Schema coverage is only 44% across 9 parameters, so the description must compensate and largely does not. It never mentions limit/offset paging, status/target/bookmaker filters, or row_id, and critically does not say which parameters apply to which of the eight actions (e.g. job_id is only for get_job/cancel_job). The brief mention of target counts and the job_payload kind values is the only parameter-adjacent meaning added.

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?

The description uses specific verbs (create, inspect, list, cancel, query) against concrete resources (async jobs, conversion history, book history), and adds a scoping threshold (>6 targets, up to 20 source codes) that hints at when the job path applies instead of direct conversion. It stops short of naming any sibling tool, so the agent must still infer how this differs from mbc_bulk_convert, mbc_split_code, or mbc_merge_codes.

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?

The description gives two useful selection conditions: use jobs for batches above the target/source-cardinality thresholds, and a plan prerequisite (Developer/Scale/Business). It gives no when-not guidance, no alternative tool names, and no mapping from the eight enum actions to scenarios (e.g. when to call get_history vs list_history, or cancel_job vs letting a job finish).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources