Casama
OfficialServer 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 |
|---|---|
| search_docsA | Keyword search over docs.casama.ai (guides, self-hosting, the API, CLI, SDKs, plugins, webhooks, A2A, bot templates, contributing). Returns the best-matching sections with their address; read a whole page with read_doc. |
| read_docA | One docs page as markdown, by path or address: "/develop/plugins", "develop/api.md" or "https://docs.casama.ai/guide/skills". Pass section to get one ## section only. |
| list_doc_pagesB | Every page on docs.casama.ai with its title and address. |
| get_api_operationA | Find operations in the Casama HTTP API (OpenAPI 3.1) and show their parameters, request body and responses as types. Query by operationId ("createBot"), "METHOD /path" ("POST /v1/conversations/{id}/messages", concrete ids work too) or keywords ("cancel run"). |
| check_pluginA | Check an Agent Plugins 1.0 folder (plugin.json, mcp.json, skills/) on this computer the way Casama checks it at install: errors (refused), warnings (skipped or ignored) and tips. |
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 5 tools
The docs tools form a clear pipeline (list_doc_pages → search_docs → read_doc) and get_api_operation and check_plugin target clearly different resources (HTTP API spec and local plugin folders). The only mild overlap is that read_doc can also surface API reference pages, so an agent could occasionally reach for it when get_api_operation would give better structured output, but the descriptions mostly steer correctly.
All five tools use a consistent verb_noun snake_case pattern: read_doc, list_doc_pages, search_docs, get_api_operation, check_plugin. Nouns are singular/plural consistently by convention (doc vs doc_pages, docs), and no mixed styles appear.
Five tools is well within the ideal range and each one has a distinct role: discovery (list/search), retrieval (read), API lookup, and local validation. Nothing appears redundant or bolted on.
Docs discovery and retrieval are fully covered, and API reference plus plugin validation round out the surface nicely. Minor gaps exist — there's no way to enumerate all API operations or pull the full OpenAPI document, and check_plugin has no companion scaffolding/init tool — but agents can work around these via keyword queries.