Skip to main content
Glama

Scb Se

by io.github.pipeworx-io

Sweden Latest Figure

sweden_latest_figure
Read-onlyIdempotent

A Swedish headline statistic as a NUMBER, for the latest month or for a month you name — "what is inflation in Sweden", "Swedish CPI in June 2026". One call — "what is inflation in Sweden", "Swedish CPI right now". Returns the figure, its unit, the exact month it refers to, and the SCB table it came from. Use this when the question asks for a number; use scb_se_subjects only when the question asks what statistics exist. Covers Swedish consumer prices today: inflation (CPI annual change) and the CPI index level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoOptional month, as "2026M06" or "2026-06" or "June 2026". Omit for the most recent published month. If the month you name has not been published yet, the response says so and names the latest month that has.
indicatorYesWhich figure: "inflation" for the CPI annual change in percent, or "cpi" for the CPI index level (2020=100). Common phrasings are understood — "inflation rate", "consumer prices", "kpi".

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "indicator": "inflation"
-  },
-  {
-    "indicator": "cpi"
-  }
-]New value: +[
+  {
+    "indicator": "inflation"
+  },
+  {
+    "indicator": "inflation",
+    "period": "2026M06"
+  },
+  {
+    "indicator": "cpi"
+  }
+]
    • addedInput schema / properties / period
      Added value: +{
+  "description": "Optional month, as \"2026M06\" or \"2026-06\" or \"June 2026\". Omit for the most recent published month. If the month you name has not been published yet, the response says so and names the latest month that has.",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful context about returned fields (figure, unit, month, SCB table) and scope, but does not mention error or edge-case behavior beyond what the schema covers.

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 and mostly concise, but example phrases are repeated twice with slight variation, making it a bit redundant. Still, all content is relevant and well-structured.

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 simple two-parameter tool with strong annotations and full schema coverage, the description is complete: purpose, usage context, return contents, and scope are all covered. No output schema exists, but the description enumerates return fields.

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?

Schema coverage is 100%, and the schema already fully describes the indicator and period parameters, including common phrasings. The description does not add significant new parameter semantics beyond what is in the schema.

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 returns a numeric Swedish headline statistic (inflation or CPI index) for the latest or a specified month, with examples. It explicitly distinguishes itself from the subjects tool by contrasting number questions with existence questions.

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?

Provides explicit guidance: use when the question asks for a number, and use the subjects tool when the question asks what statistics exist. Also clarifies one-call behavior and the optional month parameter.

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