Skip to main content
Glama

Scb Se

by io.github.pipeworx-io

Scb Se Statistical News

scb_se_statistical_news
Read-onlyIdempotent

What Statistics Sweden (SCB) has JUST PUBLISHED — the statistical news releases (statistiknyheter) from the last few days, with headline, summary, publication date and the statistical product each belongs to. Answers "vilka statistiknyheter har SCB publicerat de senaste 3 dagarna", "what did Statistics Sweden publish this week", "senaste statistiknyheterna från SCB". Swedish headlines by default; pass lang="en" for the English titles. For releases still to come rather than already out, use scb_se_publishing_calendar. Read from the SCB website listing, so the field shapes depend on SCB markup rather than a published API contract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of the window as YYYY-MM-DD. Defaults to today.
daysNoHow many days back from today, e.g. 3 for "de senaste 3 dagarna". Default 7. Ignored when from/to are given.
fromNoStart of the window as YYYY-MM-DD, e.g. "2026-08-07".
langNo"sv" (default) for Swedish headlines, "en" for English.
limitNoMaximum news items to return. Default 50, max 200.

Schema Changelog

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

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Even with readOnly/open/idempotent annotations, the description adds important implementation context: the tool reads from the SCB website listing rather than a published API contract, so field shapes can vary. It also discloses the Swedish-by-default and lang='en' behavior.

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?

The description is front-loaded and reasonably concise, with each sentence serving a purpose: defining the resource, giving usage examples, and noting exclusions. It is slightly verbose with the query examples, but still well-organized.

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 retrieval tool with no output schema, the description gives sufficient context about return fields, language behavior, date-window defaults, the source's non-API nature, and the relevant sibling tool for future releases.

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 schema description covers all 100% of parameters, so the baseline is 3. The tool description adds some context about lang and recent-window usage, but does not substantively extend the schema's per-parameter 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 explicitly defines the tool as retrieving recently published Statistics Sweden statistical news releases, listing the included fields: headline, summary, publication date, and statistical product. It also clearly differentiates itself from the publishing-calendar sibling by focusing on already-published content.

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 provides explicit example queries in Swedish and English, states the default behavior (last few days, Swedish headlines), and tells users which sibling tool to use for upcoming rather than already-published releases.

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