Skip to main content
Glama

Scb Se

by io.github.pipeworx-io

Subjects

subjects
Read-onlyIdempotent

CATALOGUE of what Statistics Sweden (SCB) publishes — the subject tree of Swedish official statistics, returned as a browsable list of subjects and table paths. Use when the question is which Swedish statistics exist or where a table lives, then scb_se_table_meta and scb_se_query_table to read figures from it. For a Swedish figure itself — inflation, CPI, and the value for a given month — sweden_latest_figure answers in one call. This listing carries no observations and no time period, so it cannot answer a question that names a month or a year. Sweden only: Canadian figures are statcan, Denmark dst-dk, Estonia stat-ee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoSub-path under /ssd/ (default empty = root).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": ""
+  },
+  {
+    "path": "BE/BE0101"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Subject tree node containing child items and metadata",
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate the tool is read-only and non-destructive. The description adds valuable context by stating the listing carries no observations and no time period, making clear it cannot answer time-bound questions. This is a useful behavioral boundary beyond the annotation hints.

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 concise, front-loaded with the core purpose, and each sentence earns its place: purpose, usage, limitation, and geography-specific alternatives. No redundant information or filler.

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?

For a low-complexity tool with one optional parameter and an output schema, the description fully covers the decision-relevant context: when to use it, what it returns, what it doesn't return, and which sibling tools to use instead for different intents. No significant gaps.

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

Parameters3/5

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

The single parameter 'path' is fully described in the input schema (sub-path under /ssd/, default empty = root). The description does not add much beyond what the schema provides, but the schema coverage is 100%, so the baseline of 3 is appropriate.

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 is a catalogue of Statistics Sweden's published subjects, returning a browsable list of subjects and table paths. It distinguishes itself from siblings by positioning itself as the discovery step before reading actual figures.

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?

Explicitly states when to use it ('which Swedish statistics exist or where a table lives'), directs to table_meta and query_table for reading figures, and names sweden_latest_figure for direct figure answers. It also lists what it cannot answer (month/year queries) and provides alternatives for other countries.

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

All Scb Se toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but several overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (only differing in verification/depth), and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread all target similar prediction-market signals, which could cause mis-selection without careful reading.

Naming Consistency4/5

Most names follow a clear verb_noun pattern (resolve_entity, query_table, remember, recall, forget, subscribe, unsubscribe, validate_claim, compare_entities, search_within), but there are exceptions like ai_visibility_check (adjective_noun), generate_llms_txt (verb_noun with dot), and several polymarket_* names that are fine but inconsistent with the snake_case verb-first convention.

Tool Count5/5

35 tools is a large but reasonable surface for a broad data/serach platform covering company financials, economics, prediction markets, memory, subscriptions, and discovery. The count is justified by the wide domain, and the set is not bloated with trivial duplicates.

Completeness4/5

The surface covers core CRUD for entities (resolve, profile, compare, search, query) and memory (remember/recall/forget), plus subscriptions and meta-tools. Minor gaps: no explicit tool for updating/creating entities (understandable for a read-only data service), and no tool for listing all available table schemas beyond discovery (subjects covers this). Overall strong coverage.

Resources