Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_creatures

Retrieve creatures from a Kanka campaign with paginated results, optional entry text, and filters for empty or filled entries to keep responses manageable.

Instructions

List creatures. 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?

No annotations exist, so the description carries the full behavioral burden. It usefully hints that responses can be large and that per_page keeps them 'small enough to be returned whole', which implies truncation risk. It does not describe read-only nature, auth requirements, or the return shape beyond that hint.

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 tightly packed sentences with the resource statement front-loaded and the parameter guidance trailing; no filler. Slightly dense phrasing in the second sentence but still efficient.

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 response-size strategy but omits the required campaignId, pagination interplay, and any indication of what each record contains. Adequate but incomplete.

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 high (80%) and the schema already explains per_page enforcement, defaults, and entry_filter's whole-collection semantics far more precisely than the description. The description's parameter sentences largely restate that, so baseline 3 applies.

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?

States a specific verb+resource ('List creatures'), which is immediately distinguishable from get_creature/create_creature/update_creature. It does not, however, contrast itself with the more general 'search' sibling or clarify that it is the scoped collection listing for creatures.

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 operational advice for two optional parameters ('Use per_page to keep responses small', 'entry_filter to return only records whose entry is empty or filled'), but never says when to pick this over search or get_creature, nor states any prerequisites like campaignId being required.

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