FCSC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FCSC_API_KEY | No | Sent as Ocp-Apim-Subscription-Key if FCSC issue an API key. | |
| FCSC_BASE_URL | No | Override the API base URL. Useful for pointing at a test stub. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listDatasetsA | Lists the official UAE statistics datasets available from FCSC, optionally filtered by topic or a free-text search over dataset names and KPIs. Use this first to find the datasetId to pass to getDatasetData. |
| getDatasetDataA | Fetches official observations for one FCSC dataset from the UAE statistics SDMX API (flat flavour) and returns them as a labelled table. Always cite these figures as official FCSC data. |
| getDatasetStructureA | Returns the dimensions and codelists for one FCSC dataset. Use this when you need to build a filtered |
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 3 tools
Each tool has a clearly distinct purpose: listing datasets, fetching data, and retrieving structure. No overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with camelCase: listDatasets, getDatasetData, getDatasetStructure. The naming is predictable and coherent.
With 3 tools, the server is well-scoped for its purpose. Each tool earns its place and covers the essential operations without excess.
The set covers the full dataset workflow: discover (listDatasets), understand (getDatasetStructure), and retrieve (getDatasetData). No significant gaps for the stated purpose.