Skip to main content
Glama
deenesjakoruzh
0xReisearch

REI Crypto MCP Server

by 0xReisearch
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_oracles

Retrieve comprehensive data on all cryptocurrency oracles across multiple protocols to monitor and analyze decentralized finance information sources.

Instructions

GET /api/oracles

Overview of all oracles across all protocols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • defillama_server.py:287-294 (handler)
    The handler function for the 'get_oracles' MCP tool. It is decorated with @mcp.tool() for automatic registration and fetches an overview of all oracles from the DefiLlama API endpoint '/api/oracles' using the shared make_request utility.
    @mcp.tool()
async def get_oracles() -> str:
    """GET /api/oracles
    
    Overview of all oracles across all protocols.
    """
    result = await make_request('GET', '/api/oracles')
    return str(result)

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions it's a GET operation (implying read-only) and returns an 'overview,' but doesn't specify what 'overview' entails (e.g., list format, pagination, rate limits, authentication needs, or data freshness). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise and front-loaded: it states the HTTP method, endpoint, and purpose in just two short sentences. There's no wasted text, and every word contributes directly to understanding the tool's basic function. This is an example of efficient communication.

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

Completeness3/5

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

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and many sibling tools, it lacks context about when to use it, what the output contains, or any behavioral constraints. The description meets the bare minimum but doesn't provide enough guidance for optimal agent use in a crowded toolset.

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 tool has 0 parameters, and schema description coverage is 100% (empty schema is fully described). The description doesn't need to explain parameters, and it correctly implies no inputs are required. A baseline of 4 is appropriate for a parameterless tool where the schema already covers everything.

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

Purpose4/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: 'Overview of all oracles across all protocols.' It specifies the verb ('GET') and resource ('oracles'), and the scope ('all oracles across all protocols') is explicit. However, it doesn't distinguish this tool from its many sibling 'get_' tools, which all follow a similar naming pattern for different resources.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With 65+ sibling tools (e.g., get_protocols, get_chains, get_stablecoins), there's no indication of how this tool relates to them or when an agent should choose it over other data retrieval options. The description merely states what it does, not when it's appropriate.

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/0xReisearch/crypto-mcp-beta'

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