Skip to main content
Glama
Sign In

Kolada Se

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Data

get_data
Read-onlyIdempotent

Fetch numeric KPI values from Kolada for a specific indicator (kpiId), Swedish municipality or region (municipalityId), and year. Returns value rows broken down by gender: T=total, K=women (kvinnor), M=men (män); non-gendered KPIs return only T.municipalityId from list_municipalities. Returns values per gender ("T" total, "K" women, "M" men); non-gendered KPIs report only "T".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2022,
      "kpiId": "N15428",
      "municipalityId": "0180"
    },
    "name": "get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit year, e.g. 2022.
kpiIdYesKPI id from search_kpi, e.g. "N15428".
municipalityIdYesMunicipality/region id from list_municipalities, e.g. "0180" (Stockholm).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "kpiId": "N15428",
+    "municipalityId": "0180",
+    "year": 2022
+  },
+  {
+    "kpiId": "N15501",
+    "municipalityId": "1480",
+    "year": 2023
+  }
+]
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent behavior. The description adds useful context about the return format (gender breakdown, non-gendered KPIs) and no contradictions. It adds beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences but contains redundancy (gender breakdown repeated). It is front-loaded with the main purpose, but could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description partly explains the return structure (gender breakdown). However, it lacks details on error cases, response format, or potential issues. The fragment 'T.municipalityId from list_municipalities' is confusing.

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% with descriptions for all parameters. The description repeats the role of parameters (e.g., 'municipalityId from list_municipalities') but adds no new syntactic or semantic details beyond what's in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches numeric KPI values for a specific indicator, municipality, and year. It uses a specific verb and resource, but does not explicitly differentiate from siblings like compare_entities or search_kpi.

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

Usage Guidelines3/5

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

The description implies that the tool is used when you have a specific kpiId, municipalityId, and year, and hints at using sibling tools (list_municipalities, search_kpi) to get IDs. However, it lacks explicit guidance on when not to use it or alternatives.

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

All Kolada Se toolsInspect
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.

Resources