Skip to main content
Glama

Describe a LINDAS data cube

describe_data_cube
Read-only

Retrieve a LINDAS statistical cube's structure, dimensions, roles, units and example values so you can query it correctly. Use the returned labels as filters in query_data_cube.

Instructions

Show the structure of one LINDAS statistical cube so you can query it: title, publisher, licence, status, dates, and every dimension with its IRI, label, role (key dimension vs measure), unit, datatype, min/max, and up to N example values with labels (sampled from the cube's value lists and observations). Use the dimension labels and example value labels as filters in query_data_cube. Example: {cube: 'https://energy.ld.admin.ch/elcom/electricityprice'}, {cube: '', examples: 20, lang: 'de'}.

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": {
      "cube": "<cube>"
    },
    "name": "describe_data_cube"
  }
}

Input Schema

NameRequiredDescriptionDefault
cubeYesCube IRI from search_data_cubes (or a visualize.admin.ch ?dataset= link)
langNoen
examplesNoExample values per key dimension (0 = skip)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. Beyond that, the description discloses that example values are 'sampled from the cube's value lists and observations' and capped at N — important behavioral context implying the output is partial rather than exhaustive. It omits any note on cost or latency of sampling large cubes.

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

Conciseness4/5

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

Front-loaded with purpose, then returned fields, then usage guidance, then a concrete example — a sensible order. The field enumeration is long but earns its place because there is no output schema, so the return shape must be described here; only minor tightening is possible.

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

Completeness5/5

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

With no output schema, the description fully carries the burden of describing return contents, and it does so field by field. Combined with the sibling handoffs and a worked example, an agent has everything needed to call it and to use its results correctly.

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 67%, and the description compensates by explaining that 'examples' returns up to N example values per key dimension and that labels are language-dependent via 'lang'. The inline example call showing {cube: ..., examples: 20, lang: 'de'} clarifies realistic usage, though it does not spell out the accepted IRI forms beyond the schema's own note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Show the structure of one LINDAS statistical cube' — and immediately enumerates what structure means (title, publisher, licence, status, dates, dimensions with IRI, role, unit, datatype, min/max, sample values). This clearly distinguishes it from query_data_cube (returns observations) and search_data_cubes (finds cubes).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear workflow handoff: use the returned dimension labels and example value labels as filters in query_data_cube, and the cube parameter points back to search_data_cubes for the IRI. It does not state explicit when-not-to-use conditions or what to do if the cube IRI is invalid, but the context is strong enough to route an agent correctly.

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