Gibraltar Prediction Markets MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Keyword search across every regulation, schedule and defined term of the Gibraltar Prediction Market Regulations 2026 (LN.2026/176). Returns ranked results with id, title, citation and a snippet. Use the returned id with |
| fetchA | Retrieve the full verbatim text of a document by its id (e.g. 'reg-12', 'schedule-2', 'definitions'). Ids come from |
| get_regulationA | Return the full verbatim text of a numbered regulation (1–34) of the Prediction Market Regulations 2026, with its Part. |
| list_regulationsA | Return the full arrangement of the Prediction Market Regulations 2026: every regulation number and title, grouped by Part, plus the three Schedules. |
| get_partA | Return the full text of every regulation within a Part (1–7) of the Prediction Market Regulations 2026. |
| get_scheduleA | Return a Schedule of the Prediction Market Regulations 2026. Schedule 1 = matters to include in an application; Schedule 2 = core authorisation conditions; Schedule 3 = modified application of the Gambling Act 2025. |
| get_definitionA | Return the interpretation (regulation 3) of a defined term, e.g. 'prediction market contract', 'authorised operator', 'settlement source'. Omit the term to list all defined terms. |
| get_application_checklistA | Return the matters that must accompany an application for a prediction market authorisation (Schedule 1, per regulation 7), as a checklist. |
| get_authorisation_conditionsA | Return the core conditions an applicant must meet for the Authority to grant a prediction market authorisation (Schedule 2, per regulation 8). |
| aboutA | Return metadata about the Prediction Market Regulations 2026 and this server: citation, enabling powers, commencement, structure and source. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| reg-1 | Regulation 1 — Prediction Market Regulations 2026 |
| reg-2 | Regulation 2 — Prediction Market Regulations 2026 |
| reg-3 | Regulation 3 — Prediction Market Regulations 2026 |
| reg-4 | Regulation 4 — Prediction Market Regulations 2026 |
| reg-5 | Regulation 5 — Prediction Market Regulations 2026 |
| reg-6 | Regulation 6 — Prediction Market Regulations 2026 |
| reg-7 | Regulation 7 — Prediction Market Regulations 2026 |
| reg-8 | Regulation 8 — Prediction Market Regulations 2026 |
| reg-9 | Regulation 9 — Prediction Market Regulations 2026 |
| reg-10 | Regulation 10 — Prediction Market Regulations 2026 |
| reg-11 | Regulation 11 — Prediction Market Regulations 2026 |
| reg-12 | Regulation 12 — Prediction Market Regulations 2026 |
| reg-13 | Regulation 13 — Prediction Market Regulations 2026 |
| reg-14 | Regulation 14 — Prediction Market Regulations 2026 |
| reg-15 | Regulation 15 — Prediction Market Regulations 2026 |
| reg-16 | Regulation 16 — Prediction Market Regulations 2026 |
| reg-17 | Regulation 17 — Prediction Market Regulations 2026 |
| reg-18 | Regulation 18 — Prediction Market Regulations 2026 |
| reg-19 | Regulation 19 — Prediction Market Regulations 2026 |
| reg-20 | Regulation 20 — Prediction Market Regulations 2026 |
| reg-21 | Regulation 21 — Prediction Market Regulations 2026 |
| reg-22 | Regulation 22 — Prediction Market Regulations 2026 |
| reg-23 | Regulation 23 — Prediction Market Regulations 2026 |
| reg-24 | Regulation 24 — Prediction Market Regulations 2026 |
| reg-25 | Regulation 25 — Prediction Market Regulations 2026 |
| reg-26 | Regulation 26 — Prediction Market Regulations 2026 |
| reg-27 | Regulation 27 — Prediction Market Regulations 2026 |
| reg-28 | Regulation 28 — Prediction Market Regulations 2026 |
| reg-29 | Regulation 29 — Prediction Market Regulations 2026 |
| reg-30 | Regulation 30 — Prediction Market Regulations 2026 |
| reg-31 | Regulation 31 — Prediction Market Regulations 2026 |
| reg-32 | Regulation 32 — Prediction Market Regulations 2026 |
| reg-33 | Regulation 33 — Prediction Market Regulations 2026 |
| reg-34 | Regulation 34 — Prediction Market Regulations 2026 |
| schedule-1 | Schedule 1 — Prediction Market Regulations 2026 |
| schedule-2 | Schedule 2 — Prediction Market Regulations 2026 |
| schedule-3 | Schedule 3 — Prediction Market Regulations 2026 |
| definitions | Regulation 3 (Interpretation) — Prediction Market Regulations 2026 |
TDQS
Scored across 10 tools
Each tool serves a distinct purpose: metadata, search, list, or retrieval of specific components (regulations, parts, schedules, definitions, checklists, conditions). No two tools overlap in functionality.
Most retrieval tools follow a consistent 'get_' prefix pattern, but 'about', 'fetch', 'search', and 'list_regulations' break this convention. While still readable, the naming is not perfectly uniform.
10 tools cover the domain of a regulatory document server comprehensively without being excessive. Each tool earns its place.
The tool set covers all necessary operations for a static legal document: metadata, search, listing, and retrieval of any component. There are no obvious gaps for the stated purpose.