Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CRACK_BROWSERNoPath to the Chrome executable (e.g. chrome.exe), used when Chrome cannot be located automatically.

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
list_my_storiesC

내 크랙 스토리 목록. storyId는 다른 도구에 넘길 ID.

get_storyB

공개된(최신 버전) 스토리의 편집용 전체 설정. 프롬프트, 시작 설정(첫 메시지) 포함.

list_story_draftsC

스토리의 임시저장 목록 (최신순).

get_story_draftC

임시저장본 하나의 전체 설정.

save_story_draftA

스토리를 임시저장한다 (공개/수정 반영은 사이트에서 직접). storyId가 있으면 최신 임시저장본(없으면 공개본)을 불러와 changes만 덮어쓴다. storyId가 없으면 새 스토리를 만든다. changes 키는 get_story 출력과 같은 이름 (name, simpleDescription, description, detailDescription, customPrompt, startingSets 등). 저장 전에 크랙 제한을 검사해 넘으면 저장하지 않고 초과 항목을 알려준다. 주요 제한: 이름 2~30자, 한 줄 소개 30자, 프롬프트 7000자, 시작설정 이름 12자·프롤로그 1000자·시작 상황 1000자·추천 답변 3개×200자, 시작설정 최대 3개, 키워드북 시작설정당 20개·키워드 5개×10자·정보 400자, 해시태그 10개×10자. 전체 표는 get_limits.

get_limitsB

크랙 스토리 빌더의 글자 수·개수 제한 전체 표.

loginA

크랙 로그인을 다시 한다. 로그인 창이 뜨면 로그인하고 창을 닫아 주세요. 보통은 필요할 때 자동으로 안내되니 직접 부를 일은 거의 없음.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation4/5

The list/get pairings (list_my_stories vs list_story_drafts, get_story vs get_story_draft) are clearly separated by resource (published vs draft), so selection should be reliable. The only real overlap is save_story_draft, which doubles as both create (no storyId) and update (with storyId), but the description spells out that behavior explicitly.

Naming Consistency4/5

All names are snake_case with a verb-first pattern (list_*, get_*, save_*), which is easy to scan and predictable. Minor deviation: login is a bare verb with no noun, and save_story_draft uses 'save' where other tools would suggest create/update.

Tool Count5/5

Seven tools is well within a healthy range and each one earns its place: two listing tools, two read tools, one write tool, plus limits and auth. Nothing looks redundant or padded for a story draft-editing workflow.

Completeness4/5

The core loop (list stories, inspect published/draft content, save draft with validation via get_limits, recover auth via login) is fully covered for the stated purpose. Gaps are deliberate or minor: publishing and reflecting edits are explicitly done on the site, but there is no tool to delete a story or draft and no search/filter over stories.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues