Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_quests

Retrieve quests from a Kanka campaign with pagination and entry filtering, and optionally omit long entry text to keep responses small.

Instructions

List quests. 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 does add real behavioral context: responses may be too large to return whole, and entry_filter applies across the entire collection rather than one API page. It stops short of disclosing mutation risk (it is a read, but that is unstated), auth requirements, or default page size behavior.

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 tight sentences, front-loaded with the purpose and then the two most consequential parameters. Nothing is wasted, though the second sentence packs two distinct ideas into one clause.

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 five-parameter list tool with no annotations and no output schema, the description covers the response-size and filtering concerns but leaves the page parameter and the entries toggle entirely to the schema. That is adequate but not complete given the missing annotation and output-schema support.

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 description coverage is 80%, so the schema already explains page, entries, per_page, and entry_filter in detail. The description reinforces per_page and entry_filter but adds no syntax or format detail beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource ('List quests'), which cleanly separates it from the mutation siblings (create_quest, update_quest, delete_quest) and the single-record get_quest. It does not explicitly differentiate from search or from other list_* siblings, which keeps it short of a 5.

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 usage advice for two parameters (use per_page to keep responses small, entry_filter for empty/filled records), which implies when those knobs matter. However, it never says when to choose list_quests over search or get_quest, nor any preconditions beyond the required campaignId.

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