Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_races

Retrieve and filter campaign races by pagination and entry status, with options to limit response size and include or omit full entry text.

Instructions

List races. Use per_page to keep responses small enough to be returned whole, and entry_filter to return only records whose entry is empty or filled.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
entriesNoInclude full entry/entry_parsed text (default true). Set false to omit the long entry fields, shrink the response, and get a has_entry boolean per record instead.
per_pageNoRecords per page, 1-100. Enforced by this server, so it holds even when the Kanka API returns a different page size. Omit to return the API's own page untouched; when set (or when entry_filter is used) the default is 25 with entries, 100 without.
campaignIdYes
entry_filterNoKeep only records with an empty entry ('empty'), only records with text ('filled'), or all of them ('all', default). Filtering is applied across the whole collection, not just one API page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / properties / entries
      Added value: +{
+  "description": "Include full entry/entry_parsed text (default true). Set false to omit the long entry fields, shrink the response, and get a has_entry boolean per record instead.",
+  "type": "boolean"
+}
    • addedInput schema / properties / entry_filter
      Added value: +{
+  "description": "Keep only records with an empty entry ('empty'), only records with text ('filled'), or all of them ('all', default). Filtering is applied across the whole collection, not just one API page.",
+  "enum": [
+    "all",
+    "empty",
+    "filled"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / page / description
      Added value: +"Page number (default 1)."
    • addedInput schema / properties / per_page
      Added value: +{
+  "description": "Records per page, 1-100. Enforced by this server, so it holds even when the Kanka API returns a different page size. Omit to return the API's own page untouched; when set (or when entry_filter is used) the default is 25 with entries, 100 without.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
  2. First observedv2.1.1

TDQS

A3.9/5.0
Behavior3/5

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

Since no annotations are provided, the description must carry the full behavioral burden. It successfully explains the operational effect of parameters, but lacks crucial details regarding potential rate limiting, required scopes, or error handling, resulting in a minimum score.

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?

The description is extremely efficient, presenting the main purpose and critical parameter instructions in a single, focused sentence without unnecessary filler.

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

Completeness4/5

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

It covers the most operationally sensitive parameters—pagination and entry filtering—providing sufficient operational context for a listing tool, even without an output schema definition.

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

Parameters4/5

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

Although schema coverage is high, the description adds semantic value by explaining the 'why' behind critical parameters, such as why 'per_page' is used to ensure the response is 'returned whole,' which is operational context not present 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 the primary function is to 'List races.' While the tool name aids specificity, the description successfully identifies the resource being acted upon.

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?

It provides specific usage advice for two complex parameters, detailing when an agent should use 'per_page' (to manage response size) and 'entry_filter' (to narrow records based on content).

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

Deploy Server

Other Tools