Skip to main content
Glama
Sign In

Kolada Se

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Kpi

search_kpi
Read-onlyIdempotent

Find Kolada KPI (indicator) ids by title substring (Swedish). Searches ~5,000 indicators covering economy, schools, health, demographics, and personnel. Returns id, title, description, operating_area, and is_divided_by_gender. Use the returned id with get_data.

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": {
      "title": "arbetslöshet"
    },
    "name": "search_kpi"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based (default 1).
titleYesSubstring of the indicator title (Swedish), e.g. "arbetslös" or "betyg".
per_pageNoResults per page (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "title": "arbetslöshet"
+  },
+  {
+    "page": 1,
+    "per_page": 50,
+    "title": "betyg"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Description adds significant behavioral context beyond annotations: it specifies the search mechanism (substring in Swedish), the number of indicators, and the exact return fields (id, title, description, operating_area, is_divided_by_gender). No contradictions with annotations.

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 sentences, front-loaded with the main action. No fluff, every sentence adds value. Efficient and clear.

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?

Despite no output schema, the description explicitly lists return fields and explains how to use the result. Covers scope, data categories, and next steps. Sufficient for an agent to understand and invoke correctly.

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%, so baseline is 3. The description does not add new parameter-level details beyond what the schema already provides (e.g., title is a Swedish substring, pagination params). Examples in schema help but description itself does not elaborate.

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 'Find Kolada KPI (indicator) ids by title substring (Swedish)' with a specific verb and resource. It distinguishes itself from sibling tools like 'get_data' by explaining the purpose and how the returned id is used.

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

Usage Guidelines4/5

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

Provides context on the scope (~5,000 indicators, categories) and explicitly instructs to use the returned id with 'get_data'. However, it lacks explicit 'when-not-to-use' or alternatives among siblings, though the sibling list is large and mostly unrelated.

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