lindas-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cubesA | Find statistical data cubes in LINDAS by topic. The entry point. Returns cube URIs you then pass to Args:
query: Topic term, e.g. "Wald", "Abfluss", "Energie". Matched against
cube names and descriptions in the chosen language.
language: Language for names and descriptions.
creator_uri: Restrict to one publishing body (from |
| get_cube_structureA | Read a cube's dimensions and measures — always call this before data. This is phase 1 of the two-phase access pattern. It tells you which
dimensions you can filter on ( Args:
cube_uri: A cube URI from |
| query_cube_observationsA | Read the actual data points of a cube, with codes resolved to labels. This is phase 2. Values are returned keyed by human-readable dimension names, and coded dimension values (e.g. region "1805") are replaced by their labels (e.g. "Alpennordhang") unless you turn that off. For large cubes this reads only the first Args:
cube_uri: A cube URI from |
| list_publishersA | List the federal bodies that publish cubes, with cube counts. Returns creator URIs you can pass to |
| resolve_municipalityA | Resolve a Swiss municipality to its LINDAS URI and BFS number. The BFS commune number is the join key across the whole portfolio: the same number identifies the municipality in swiss-statistics-mcp, zurich-opendata-mcp and any cube that references a place. In LINDAS the URI is literally ld.admin.ch/municipality/. Args: name_or_bfs: A municipality name ("Zürich") or a BFS number ("261"). language: Language for the name. |
| run_sparqlA | Run a raw SPARQL SELECT query. Advanced escape hatch — use sparingly. Prefer the structured tools. This exists for analytical queries the guarded tools cannot express (cross-cube joins, aggregations, custom filters). Guardrails, learned from probing: LINDAS times out on unanchored scans, so
always anchor on a known class such as Args: query: A complete SPARQL SELECT query, including its own PREFIX lines. |
| api_statusA | Check whether the LINDAS SPARQL endpoint is reachable. Returns an evaluable status even on failure, so an agent can tell "no data matched" apart from "the endpoint is down". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/lindas-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server