Skip to main content
Glama
pythia-the-oracle

pythia-oracle-mcp

Official

get_market_summary

Retrieve a system-wide summary of all tokens tracked by Pythia, including operational status, uptime distribution, and data source health for quick system health assessment.

Instructions

Get a summary of all tokens tracked by Pythia with operational overview.

Returns system-wide stats, tokens grouped by status, uptime distribution, data source health, and infrastructure status. Useful for quickly understanding what Pythia covers and whether the system is healthy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_market_summary tool handler function. Fetches live data from feed-status.json and returns a system overview with tokens grouped by status, ecosystem coverage, data source health, and infrastructure status.
    @mcp.tool()
    async def get_market_summary() -> str:
        """Get a summary of all tokens tracked by Pythia with operational overview.
    
        Returns system-wide stats, tokens grouped by status, uptime distribution,
        data source health, and infrastructure status. Useful for quickly
        understanding what Pythia covers and whether the system is healthy.
        """
        data = await _fetch_data()
        tokens = data.get("tokens", [])
        stats = data.get("stats", {})
        system = data.get("system", {})
        generated = data.get("generated_at", "unknown")
    
        lines = [f"Pythia Oracle — System Overview (as of {generated})\n"]
    
        # Overall stats
        lines.append("System Stats:")
        lines.append(f"  Tokens:           {stats.get('tokens', '?')}")
        lines.append(f"  Indicator feeds:  {stats.get('total_indicators', '?')}")
        lines.append(f"  Chains:           {stats.get('chains', '?')}")
        lines.append(f"  Ecosystems:       {stats.get('ecosystems', '?')}")
        lines.append(f"  Avg response:     {stats.get('avg_response_ms', '?')}ms")
        lines.append(f"  Active incidents: {stats.get('active_incidents', 0)}")
        lines.append("")
    
        # Tokens by status
        by_status: dict[str, list[str]] = {}
        for t in tokens:
            s = t.get("status", "unknown")
            by_status.setdefault(s, []).append(t["symbol"])
    
        lines.append("Tokens by Status:")
        for status in ["live", "warn", "down", "unknown"]:
            if status in by_status:
                syms = ", ".join(sorted(by_status[status]))
                lines.append(f"  {status:<6} ({len(by_status[status])}): {syms}")
        lines.append("")
    
        # Tokens by ecosystem
        by_eco: dict[str, list[str]] = {}
        for t in tokens:
            eco = t.get("ecosystem", "Other")
            by_eco.setdefault(eco, []).append(t["symbol"])
    
        lines.append("Coverage by Ecosystem:")
        for eco, syms in sorted(by_eco.items(), key=lambda x: -len(x[1])):
            lines.append(f"  {eco:<20} {len(syms)} tokens: {', '.join(sorted(syms))}")
        lines.append("")
    
        # Data sources
        sources = system.get("sources", [])
        if sources:
            lines.append("Data Sources:")
            for s in sources:
                lines.append(f"  {s['name']:<15} status: {s['status']}  (tier {s['tier']})")
            lines.append("")
    
        # Infrastructure
        infra = system.get("infrastructure", {})
        if infra:
            lines.append("Infrastructure:")
            for component, status in infra.items():
                lines.append(f"  {component:<15} {status}")
    
        return "\n".join(lines)
  • Registration via @mcp.tool() decorator on the async function get_market_summary. The FastMCP instance 'mcp' is created at line 17.
    @mcp.tool()
    async def get_market_summary() -> str:
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries the burden of disclosing behavioral traits. It explains the output content but does not mention any side effects, rate limits, authentication requirements, or latency considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the main action 'Get a summary', and directly lists key contents without unnecessary words. It is concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and the presence of an output schema, the description is complete. It adequately explains the tool's purpose and output, and the sibling context shows this tool as a high-level overview.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the input schema provides full coverage. The description adds meaning by detailing what the summary contains, which is valuable context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a summary of all tokens tracked by Pythia with an operational overview, listing specific contents like system-wide stats, tokens grouped by status, uptime distribution, data source health, and infrastructure status. This distinguishes it from siblings that focus on specific tokens or feeds.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies it is useful for quickly understanding Pythia's coverage and system health, providing clear when-to-use context. However, it does not explicitly state when not to use this tool or mention alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pythia-the-oracle/pythia-oracle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server