Skip to main content
Glama

SPARQL query on LINDAS

query_lindas
Read-only

Runs read-only SPARQL SELECT queries against lindas.admin.ch to retrieve Swiss federal linked data, including energy prices, legislation, municipality records, and statistical cubes.

Instructions

Run a read-only SPARQL SELECT query against lindas.admin.ch, the Swiss federal linked-data service. Useful graphs include https://lindas.admin.ch/elcom/electricityprice (energy prices), ELI legislation, the municipality register (ld.admin.ch/municipality/{BFS}), and cube.link statistical cubes. A top-level LIMIT of 100 is added if none is given and larger limits are clamped to 200; SERVICE (federation) and update operations are rejected; max 10000 characters.

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": {
      "query": "<query>"
    },
    "name": "query_lindas"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSPARQL SELECT query (read-only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing implicit LIMIT injection at 100, clamping of larger limits to 200, rejection of SERVICE federation and update operations, and a 10000-character cap. The only missing behavior is what the result payload looks like (bindings format, error shape), which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the endpoint and operation, followed by graph hints and then hard constraints. No filler or restatement of the name.

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?

For a single-parameter, open-world query tool with no output schema, the definition covers endpoint, useful graphs, and all enforced limits. The remaining gap is return-value shape, which the description must carry alone in the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics the schema does not: that LIMIT is auto-injected and clamped, which changes how an agent should write paging queries. It also reinforces the SELECT-only restriction beyond the schema's parenthetical.

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 and resource ('Run a read-only SPARQL SELECT query against lindas.admin.ch') and identifies the service as the Swiss federal linked-data endpoint. This implicitly separates it from query_wikidata and query_dataset, though no sibling is named explicitly.

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?

Gives useful orientation on which graphs exist (electricity prices, ELI legislation, municipality register, cube.link cubes), which helps an agent decide the tool is relevant. However, it never states when to prefer this over query_wikidata or query_data_cube, nor any exclusions beyond the query-language constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools