Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DF_ASSET_PROJECT_IDNoOptional override for the Asset Hub project namespace. Defaults to ikaos-story-2026.ikaos-story-2026
DF_ASSET_UPLOAD_URLNoOptional override for the Asset Hub upload URL. Defaults to https://df-asset-hub.vercel.app/api/review/figma-images/upload.https://df-asset-hub.vercel.app/api/review/figma-images/upload
IKAOS_STORY_API_URLYesThe base URL of the iKAOS Story API.
IKAOS_STORY_API_TOKENYesYour project-scoped API token for the Story API.

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
upload_story_imageC

Upload a local PNG, JPG, JPEG, or WebP file to Asset Hub after verifying the Story image slot.

update_story_imageB

Replace an Asset Hub image file using the scoped image ID returned by upload_story_image.

list_storiesA

List iKAOS Story IDs and their read-only delivery status.

get_story_contextA

Read one Story identity, authoritative document receipt, current data, revision, and preview URL.

get_story_rulesA

Read one immutable Story workflow, semantic, Quote, catalog, or producer rule file.

save_story_contentA

Create or modify Story content/layout JSON with optimistic revision protection. Fixed docs and source metadata cannot be changed.

validate_storyC

Validate the current Supabase Story content structure and identity.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct resource or action: listing vs. single-story context, reading rules vs. content, saving vs. validating, and uploading vs. updating images. Even the two image tools are clearly separated by their roles in the upload/replace workflow.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern, such as list_stories, get_story_context, save_story_content, and validate_story. No mixed casings or stylistic deviations appear.

Tool Count5/5

Seven tools is a well-scoped set for a story management server. Each tool covers a meaningful part of the workflow without redundancy or excessive granularity.

Completeness4/5

The set covers listing, reading, creating/updating content, validating, and managing images, which handles the core story lifecycle. The main gap is the absence of an explicit delete operation for stories or images, though this may be intentional given the immutable/revision-oriented design.

Maintenance

ActivityMaintained
ResponsivenessNo issues