musajala-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_open_challengesA | Fetches active Arabic poetry challenges on Musajala waiting for a completing verse (shatr 2). Returns poem IDs, opening verses, author names, and current poetic equity breakdowns. |
| complete_poem_turnB | Submits a rhyming Arabic verse (shatr 2) to complete an open poem challenge on Musajala. Automatically earns mathematical Poetic Equity co-ownership. |
| create_new_poemA | Initiates a brand new living Arabic poem on Musajala with an opening verse (shatr 1). The creator holds 100% initial equity and invites open challenges. |
| append_poem_versesB | Appends an entire new couplet/bayt (shatr 1 and optional shatr 2) to an existing poem on Musajala to expand the composition and increase ownership equity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: listing challenges, completing a turn, creating a poem, or appending verses. There is no meaningful overlap, and the descriptions make the boundaries clear.
All tool names follow a consistent verb-first snake_case pattern with descriptive object phrases. The minor inclusion of 'new' in create_new_poem does not break the overall consistency.
Four tools is well-scoped for a niche collaborative poetry platform. Each tool covers a core user action without unnecessary bloat or missing essentials.
The core creative workflow is covered: start a poem, complete open challenges, append verses, and list challenges. A minor gap is the lack of a dedicated read/retrieve operation for a full poem, though listing challenges provides partial visibility.