Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_calendars

Retrieve calendars for a Kanka campaign, with filters for empty or filled entries and page-size controls to keep responses manageable.

Instructions

List calendars. 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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one non-obvious trait: per_page keeps responses "small enough to be returned whole," implying responses can otherwise be truncated. That is useful, but it says nothing about read-only nature, permissions, pagination defaults, or total-count behavior for a collection-listing tool.

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?

Two sentences, no filler, and the resource is stated first followed by the two most operationally important parameters. The only weakness is that the parameter hints are compressed into one long sentence rather than structured.

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?

For a 5-parameter list tool with no annotations and no output schema, the description covers response-size and filtering behavior but omits pagination mechanics, the required campaignId scope, and what a record contains. It is adequate to call correctly but leaves real gaps an agent would have to discover by reading the schema.

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 80%, so the schema already documents page, entries, per_page and entry_filter thoroughly. The description adds marginal value by framing per_page as a response-size safeguard rather than just a count, but it says nothing about campaignId (the only required param) or the page parameter, so it does not compensate for the remaining gap.

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 opens with a specific verb+resource ("List calendars"), which unambiguously identifies it against the get/create/update/delete_calendar siblings. It does not distinguish itself from the many other list_* siblings or from search, but the resource is clear enough that an agent knows what it retrieves.

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?

It gives parameter-level guidance (use per_page to keep responses small, use entry_filter to narrow by entry state), which implies when the tool is useful. However, it never states when to prefer list_calendars over search or get_calendar, nor any prerequisite beyond the implicit campaign scope.

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