Scb Se

Table Meta

table_meta

Read-onlyIdempotent

Dimension definitions and valid filter values for one Statistics Sweden (SCB) table of SWEDISH official statistics (e.g. "BE/BE0101/BE0101A/BefolkningNy"). Required before scb_se_query_table so you know which codes to pass. Find the table path with scb_se_subjects first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	e.g. "BE/BE0101/BE0101A/BefolkningNy"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`variables`	No	List of dimensions/variables in the table

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "path": "BE/BE0101/BE0101A/BefolkningNy"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Table metadata including dimensions and valid values",
+  "properties": {
+    "variables": {
+      "description": "List of dimensions/variables in the table",
+      "items": {
+        "properties": {
+          "code": {
+            "description": "Variable code",
+            "type": "string"
+          },
+          "text": {
+            "description": "Variable label",
+            "type": "string"
+          },
+          "valueTexts": {
+            "description": "Labels for values",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "values": {
+            "description": "Valid values for this dimension",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, and non-destructive behavior, lowering the bar. The description adds that this is a prerequisite and provides metadata for querying, offering useful context beyond the annotations without contradicting them.

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?

The description is three sentences, each serving a distinct purpose: defining the tool, stating its prerequisite role, and directing how to find the path. No wasted words.

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 one parameter, an output schema, and strong annotations, the description fully covers the tool's role in the workflow. It explains why to use it and how it relates to other tools, making it complete for an agent.

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% for the single 'path' parameter, which already includes a description and example. The description reinforces the path format with an example and adds the dependency context, slightly enhancing the schema's semantics.

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?

The description clearly states the tool provides dimension definitions and valid filter values for a specific Statistics Sweden table, with an example path. This makes its purpose distinct from sibling tools like query_table (data retrieval) and subjects (path discovery).

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

Usage Guidelines5/5

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

It explicitly instructs to use this tool before scb_se_query_table and after scb_se_subjects, establishing a clear sequence and naming the alternative tools. This is excellent guidance on when and how to use the tool.

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

All Scb Se tools Inspect

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.