Skip to main content
Glama
pythia-the-oracle

pythia-oracle-mcp

Official

get_token_feeds

Get all indicator feeds for a token, including feed names (EMA, RSI, Bollinger, Volatility across timeframes), reliability stats, and data source count.

Instructions

Get all available indicator feeds for a specific token.

Shows every feed name (EMA, RSI, Bollinger, Volatility across all timeframes), the token's reliability stats, and data source count. Feed names are what you pass to the on-chain oracle to request data.

Args: engine_id: Token engine ID (e.g., 'bitcoin', 'solana', 'bittensor', 'aave', 'pol'). Use list_tokens() to see all available IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engine_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_token_feeds' tool handler function. It retrieves all available indicator feeds for a specific token by engine_id, fetches live data from feed-status.json, looks up the token, groups feeds by indicator type (EMA, RSI, Bollinger, Volatility), and returns a formatted report.
    @mcp.tool()
    async def get_token_feeds(engine_id: str) -> str:
        """Get all available indicator feeds for a specific token.
    
        Shows every feed name (EMA, RSI, Bollinger, Volatility across all
        timeframes), the token's reliability stats, and data source count.
        Feed names are what you pass to the on-chain oracle to request data.
    
        Args:
            engine_id: Token engine ID (e.g., 'bitcoin', 'solana', 'bittensor',
                       'aave', 'pol'). Use list_tokens() to see all available IDs.
        """
        data = await _fetch_data()
        tokens = data.get("tokens", [])
    
        token = next((t for t in tokens if t["engine_id"] == engine_id), None)
        if not token:
            available = sorted(t["engine_id"] for t in tokens)
            return (
                f"No token found for '{engine_id}'.\n\n"
                f"Available: {', '.join(available)}"
            )
    
        feed_names = token.get("feed_names", [])
        lines = [
            f"{token['symbol']} ({token['name']}) — {token.get('pair', '?')}",
            f"Status: {token.get('status', '?')}  |  "
            f"30d uptime: {token.get('uptime_30d', '?')}%  |  "
            f"Data sources: {token.get('sources', '?')}",
            f"Category: {token.get('category', '?')}  |  "
            f"Ecosystem: {token.get('ecosystem', '?')}",
            f"\n{len(feed_names)} indicator feeds available:\n",
        ]
    
        # Group by indicator type
        groups: dict[str, list[str]] = {}
        for name in sorted(feed_names):
            # Strip token prefix to get indicator part
            suffix = name[len(engine_id) + 1:]
            cat = suffix.split("_")[0]
            groups.setdefault(cat, []).append(suffix)
    
        for cat, feeds in sorted(groups.items()):
            lines.append(f"  {cat}:")
            for feed in feeds:
                lines.append(f"    {engine_id}_{feed}")
            lines.append("")
    
        lines.append("To request any feed on-chain, pass the full feed name")
        lines.append("(e.g., 'bitcoin_RSI_1H_14') to the Pythia consumer contract.")
        lines.append(f"\nUse get_integration_guide() for Solidity code.")
        return "\n".join(lines)
  • The @mcp.tool() decorator registers 'get_token_feeds' as an MCP tool on the FastMCP instance.
    @mcp.tool()
Behavior4/5

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

Without annotations, the description carries the full behavioral burden. It details what the tool returns (feed names, reliability stats, data source count), implying a read-only operation. No contradictions, but it lacks explicit statements about side effects or authentication requirements, which are not critical for this simple get tool.

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

Conciseness4/5

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

The description is concise at about four sentences, includes a structured Args section, and avoids redundancy. However, the first two sentences could be merged, and the flow is slightly disjointed.

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 the tool's simplicity (one parameter, no nested objects, output schema exists), the description covers all essential aspects: what it does, what it returns, how to use the parameter, and a pointer to a sibling tool. No gaps are apparent.

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?

The schema has 0% description coverage for the parameter, so the description compensates by explaining engine_id with examples and a reference to list_tokens(). This adds meaningful guidance beyond the empty schema, though a more formal description in the schema would be better.

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 the tool's purpose with a specific verb ('Get') and resource ('available indicator feeds') tied to a token. It distinguishes from siblings like get_feed_value (which retrieves individual feed values) and list_tokens (which lists token IDs).

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 provides context by noting that feed names are passed to the on-chain oracle and advises using list_tokens() to find valid engine_id values. However, it does not explicitly state when to use this tool versus alternatives like get_feed_value, leaving some ambiguity.

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