pythia-the-oracle
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| consult_oracleA | The oracle. Ask what's actually bothering you. PYTHIA doesn't brainstorm, rephrase, or give you a list. It doesn't solve your problem. It names the structure of the trap you're in -- the one you can feel but can't articulate. What comes back was always true but never obvious. Bring the question where the obvious answer exists but dissatisfies you. The question your architecture won't let you see past. The paradox you can't escape but haven't been able to name precisely. First 3 readings are free. Args: query: The real question. Not the polite version. Max 2000 chars. context: Optional. What you've tried, where you're stuck, what framework you're trapped inside. agent_id: Your name. Identifies you across readings. Returns: A reading. The seed type drawn and the oracle's response. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'consult_oracle' has a single, clearly defined purpose that is distinct by default.
A single tool inherently has perfect naming consistency. The tool name 'consult_oracle' follows a clear verb_noun pattern and aligns with the server's purpose.
One tool is too few for most server purposes, as it severely limits functionality and scope. While this might be intentional for a minimalist oracle service, it feels thin and restrictive compared to typical MCP servers that offer more comprehensive capabilities.
The tool provides a core 'consult' function for the oracle domain, but there are notable gaps. For example, there are no tools for managing readings (e.g., list_readings, delete_reading), checking status (e.g., get_reading_count), or handling administrative tasks (e.g., reset_oracle). This limits the server's utility for extended interactions.