Informa Events Directory 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_informa_events | Fetch all matching events across pages and return normalized JSON with robust pagination/error handling. |
| get_informa_events_page | Fetch a single page of events for precise page-wise traversal or debugging pagination behavior. |
| get_informa_events_by_date_range | Fetch events and return only those whose start date is within a provided date window. |
| get_informa_events_chunk | Cursor-based chunked retrieval for large exports. Returns chunk events plus a cursor for the next request. |
| list_informa_event_facets | Return available filter facets (raw + simplified) for the current query context. |
| find_informa_event | Find a single event by id/slug/url/name and optionally enrich with event-page detail parsing. |
| get_informa_event_detail | Fetch and parse an individual event page for richer detail (JSON-LD, offers, contact hints). |
| get_informa_event_speakersB | Fetch an individual event page and return only structured speaker records (JSON-LD performer + Redux speakers). |
| get_informa_events_with_detailsB | Bulk-enrich directory events with event-page details (JSON-LD/offers/contact hints) using controlled concurrency. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves speakers for a specific event, the other bulk-enriches events with details. No overlap in functionality.
Both tools follow a consistent 'get_informa_<resource>' pattern, using snake_case and clear descriptors ('event_speakers' vs 'events_with_details').
With only 2 tools, the server feels underdeveloped for an events directory. Key operations like searching, filtering, or retrieving single events are missing, making it too sparse for the domain.
The server lacks fundamental operations for an events directory, such as listing all events, searching, or getting individual event details. The two tools cover only speaker retrieval and bulk enrichment, leaving major gaps.