Skip to main content
Glama

Cbs Il

by io.github.pipeworx-io
OverviewAdmin

Catalog Browse

catalog_browse
Read-onlyIdempotent

Browse the CBS time-series catalog. With no subject_id, returns the top-level subjects (Foreign Trade, Population, Balance of Payments, Consumer Price Index, etc.) — each with a numeric path id. Pass that id back as subject_id to drill into a subject's full set of leaf series paths. The catalog is hierarchical; each catalog entry has a 'path' breadcrumb array and a 'name'. Use this to discover what's available before calling get_series_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoContent language. Default "en".
pageNoPage number for paginated leaf lists (default 1, page size 100).
subject_idNoTop-level subject id (from a no-arg call, e.g. 8 = Foreign Trade, 2 = Population). Omit to list the top-level subjects.

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "subject_id": 8
+  },
+  {
+    "lang": "en",
+    "page": 1
+  }
+]
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), description adds hierarchical behavior: returns top-level subjects with ids, drilling down yields leaf series paths with breadcrumb and name. No contradictions.

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?

Two paragraphs, every sentence adds value. No fluff. Front-loaded with the main verb and resource.

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?

No output schema, but description fully explains return structure: top-level subjects with path ids, leaf series with path breadcrumb and name. Covers all 3 parameters adequately.

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

Parameters5/5

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

With 100% schema coverage, baseline 3. Description adds significant value: explains subject_id as id from no-arg call with examples (8=Foreign Trade), page for paginated leaf lists, and lang for language.

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 it browses a CBS time-series catalog, explains the hierarchical structure, and distinguishes from get_series_data. It uses specific verbs like 'browse' and 'discover what's available'.

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: 'before calling get_series_data' to discover what's available. Also implies when not to use (for data retrieval, use get_series_data).

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

All Cbs Il 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.

Resources