Skip to main content
Glama

OpenHelvetia Gateway

by swiss.openhelvetia
OverviewDiscussionsAdmin

lindas.observations

Read-only

Read a cube's rows with filters (Abstimmung, Referendum, Volksinitiative, Ständemehr, Kanton, Datum): use for the figures themselves. norm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cubeYes
langNo
limitNo
offsetNo
filtersNoFilters, one per entry: the object `{dimension, value}` — `{"dimension": "https://politics.ld.admin.ch/political-rights/popular-vote/date", "value": "1971-02-07"}` — or, equally accepted, the string `dimension=value`. The dimension is the full IRI `lindas.describe_cube` served, the value an IRI or a plain literal. A dimension the shape does not declare is admitted when the cube's observations carry it, and the answer says so.
dimensionsNoThe dimension IRIs to project — the cells a row comes back with. Absent = every cell the row carries, which is up to 51 in the vote cube; naming the three or four a question needs is one call instead of paging the same table at a smaller limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / filters / description
      Previous value: -"Filters, ONE STRING per filter in the form `dimension=value` —\n`https://politics.ld.admin.ch/political-rights/popular-vote/date=1971-02-07`\n— never an object. The dimension is the full IRI\n`lindas.describe_cube` served, the value an IRI or a plain\nliteral. A dimension the shape does not declare is admitted\nwhen the cube's observations carry it, and the answer says so."New value: +"Filters, one per entry: the object `{dimension, value}` —\n`{\"dimension\": \"https://politics.ld.admin.ch/political-rights/popular-vote/date\",\n\"value\": \"1971-02-07\"}` — or, equally accepted, the string\n`dimension=value`. The dimension is the full IRI\n`lindas.describe_cube` served, the value an IRI or a plain\nliteral. A dimension the shape does not declare is admitted\nwhen the cube's observations carry it, and the answer says so."
    • addedInput schema / properties / filters / items / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "description": "`{dimension, value}` — the canonical form.",
+    "properties": {
+      "dimension": {
+        "description": "The dimension IRI as `lindas.describe_cube` served it.",
+        "type": "string"
+      },
+      "value": {
+        "description": "An IRI (matched exactly) or a plain literal.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "dimension",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "`dimension=value` — the FIRST `=` separates them.",
+    "type": "string"
+  }
+]
    • addedInput schema / properties / filters / items / description
      Added value: +"One filter: the object `{dimension, value}`, or the string\n`dimension=value`."
    • removedInput schema / properties / filters / items / type
      Removed value: -"string"
  2. Changed1 schema field changed
    • changedInput schema / properties / filters / description
      Previous value: -"Filters as `dimension=value` pairs; the dimension is the full\nIRI `lindas.describe_cube` served, the value an IRI or a plain\nliteral. A dimension the shape does not declare is admitted\nwhen the cube's observations carry it, and the answer says so."New value: +"Filters, ONE STRING per filter in the form `dimension=value` —\n`https://politics.ld.admin.ch/political-rights/popular-vote/date=1971-02-07`\n— never an object. The dimension is the full IRI\n`lindas.describe_cube` served, the value an IRI or a plain\nliteral. A dimension the shape does not declare is admitted\nwhen the cube's observations carry it, and the answer says so."
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and the description's 'Read' is consistent, so no contradiction. The description adds that filtering is possible and names relevant dimensions, but does not disclose pagination, response shape, or any other behavioral details; the annotation carries most of the safety profile.

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

Conciseness2/5

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

Very short, but the trailing 'norm.' and the phrase 'the figures themselves' are cryptic and under-specified. It is concise in length, but not clearly structured or self-explanatory.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters and no output schema, this is a non-trivial tool, yet the description says nothing about cube selection, language, limit behavior, or row shape. It lacks the richness needed for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 33% — cube, lang, limit, and offset are undocumented in the schema. The description names a few filter dimensions but omits all other parameters entirely, so it fails to compensate for the coverage gap.

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 clear verb ('Read') and resource ('a cube's rows'), with a list of filter dimensions that hint at the vote-cube domain. It doesn't explicitly contrast with sibling tools like lindas.dimension_values, so it's clear but not sharply differentiated.

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?

The phrase 'use for the figures themselves' gives some situational context, but no exclusions or alternatives are named (e.g., when to prefer lindas.dimension_values). Guidance is implied rather than explicit.

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

All OpenHelvetia Gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources