Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KANKA_API_TOKENYesYour Kanka API token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_campaignsA

List all campaigns

searchC

Search entities

list_charactersC

List characters

get_characterB

Get details of a character

create_characterC

Create a new character

update_characterC

Update an existing character

delete_characterC

Delete an existing character

list_locationsD

List locations

get_locationC

Get details of a location

create_locationD

Create a new location

update_locationC

Update an existing location

delete_locationC

Delete an existing location

list_familiesC

List families

get_familyC

Get details of a family

create_familyC

Create a new family

update_familyC

Update an existing family

delete_familyC

Delete an existing family

list_organisationsD

List organisations

get_organizationC

Get details of a organization

create_organizationC

Create a new organization

update_organizationC

Update an existing organization

delete_organizationC

Delete an existing organization

list_itemsD

List items

get_itemC

Get details of a item

create_itemC

Create a new item

update_itemC

Update an existing item

delete_itemC

Delete an existing item

list_notesD

List notes

get_noteB

Get details of a note

create_noteC

Create a new note

update_noteC

Update an existing note

delete_noteB

Delete an existing note

list_eventsC

List events

get_eventC

Get details of a event

create_eventD

Create a new event

update_eventC

Update an existing event

delete_eventC

Delete an existing event

list_calendarsC

List calendars

get_calendarC

Get details of a calendar

create_calendarC

Create a new calendar

update_calendarC

Update an existing calendar

delete_calendarC

Delete an existing calendar

list_timelinesD

List timelines

get_timelineC

Get details of a timeline

create_timelineD

Create a new timeline

update_timelineC

Update an existing timeline

delete_timelineC

Delete an existing timeline

list_creaturesD

List creatures

get_creatureC

Get details of a creature

create_creatureC

Create a new creature

update_creatureC

Update an existing creature

delete_creatureC

Delete an existing creature

list_racesC

List races

get_raceC

Get details of a race

create_raceD

Create a new race

update_raceC

Update an existing race

delete_raceC

Delete an existing race

list_questsD

List quests

get_questB

Get details of a quest

create_questC

Create a new quest

update_questC

Update an existing quest

delete_questC

Delete an existing quest

list_mapsD

List maps

get_mapC

Get details of a map

create_mapC

Create a new map

update_mapC

Update an existing map

delete_mapC

Delete an existing map

list_journalsD

List journals

get_journalC

Get details of a journal

create_journalC

Create a new journal

update_journalC

Update an existing journal

delete_journalB

Delete an existing journal

list_abilitiesC

List abilities

get_abilityC

Get details of a ability

create_abilityC

Create a new ability

update_abilityC

Update an existing ability

delete_abilityD

Delete an existing ability

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 77 tools

Disambiguation4/5

Each entity type has a clear list/get/create/update/delete set, so tools are mostly distinguishable by resource and action. The main confusion points are the organisations/organization spelling mismatch and campaigns having only list_campaigns, but there is no genuine functional overlap.

Naming Consistency4/5

Tool names follow a consistent list_plural/get_singular/create_singular/update_singular/delete_singular snake_case pattern across nearly all entities. Minor deviations like `list_organisations` vs `get_organization` and the bare `search` prevent a perfect score.

Tool Count2/5

77 tools is far beyond the typical well-scoped MCP surface and will impose a heavy context burden on agents. While the repetition is systematic, covering 15 entity types with full CRUD creates excessive bloat for what is ultimately a single domain.

Completeness4/5

The server covers full CRUD for most major Kanka entity types, which is strong domain coverage. The notable gap is campaigns: only list_campaigns exists, with no get/create/update/delete, and some secondary Kanka features like tags or relations are absent.

Maintenance

ActivityInactive
ResponsivenessNo issues