Skip to main content
Glama

GambleMath — Casino RTP, Bonus EV & UKGC Register Lab

lookup_ukgc_domain

Verify a casino domain against the 2026-10-19 UKGC Public Register snapshot (account #, licensee entity, domain status).

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": {
      "domain": "<domain>"
    },
    "name": "lookup_ukgc_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name (e.g. foxygames.com, 32red.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that results come from a fixed 2026-10-19 snapshot (i.e., data may be stale rather than live) and enumerates the returned fields, but it never states that the operation is read-only, how a non-match is reported, or any access/rate constraints.

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 front-loaded sentence with the verb and data source first and the return fields scoped in parentheses; nothing is redundant, though the parenthetical is slightly compressed.

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?

With one parameter, no annotations and no output schema, the description does the important work of naming the data source, its snapshot date, and the fields returned. The main remaining gap is negative-result behavior (domain not in register) and staleness implications.

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 the schema already gives the parameter description plus concrete examples. The description only adds the qualifier 'casino', so it contributes little meaning beyond the structured field — baseline 3.

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 (Verify) and resource (casino domain) against a named data source (UKGC Public Register snapshot), and the parenthetical names the returned fields. This clearly distinguishes it from the sibling audit/simulation tools, though it does not explicitly route away from any of them.

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 'Verify a casino domain' — an agent can infer this is for checking a domain's licensing status — but there is no explicit when-to-use/when-not guidance, no prerequisite statements, and no mention of what to do when a domain is absent from the register.

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