MCP Spine
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
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spine_set_contextA | Tell the Spine what you are currently working on. This re-routes which tools are visible to you based on your current task. |
| spine_recallA | Recall cached results from previous tool calls. Use this to check what a tool returned earlier without re-calling it, especially if that tool is no longer in your active tool set. |
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 2 tools
spine_set_context and spine_recall have completely distinct roles: one writes/updates the current work context and changes tool visibility, the other reads cached results from prior calls. There is no overlap or plausible selection confusion.
Both tool names follow the same spine_<verb> pattern and use snake_case. The verbs set_context and recall are clear and parallel, so an agent can predict tool naming.
At two tools, the server is below the typical 3-15 tool range, but the scope is narrow and each tool serves one essential function: updating context and recalling cached results. The count is slightly under but still reasonable for its purpose.
The server covers the core context-setting and cache-recall workflows without obvious dead ends. Minor gaps exist (no explicit clear-context or clear-cache operation), but set_context can overwrite context and recall covers the main retrieval need.