Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_emissions

Retrieve token emissions data for cryptocurrency analysis using integrated DeFiLlama, CoinGecko, and Arkham Intelligence APIs.

Instructions

GET /api/emissions

List of all tokens along with basic info for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_emissions' tool. It makes a GET request to the DefiLlama /api/emissions endpoint using the shared make_request helper and returns the JSON response as a string. The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    async def get_emissions() -> str:
        """GET /api/emissions
        
        List of all tokens along with basic info for each.
        """
        result = await make_request('GET', '/api/emissions')
        return str(result)
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 implies a read-only operation via 'GET' and 'List', but doesn't specify details like pagination, rate limits, authentication requirements, or what constitutes 'basic info'. 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.

Conciseness4/5

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

The description is brief and front-loaded, consisting of two sentences: the HTTP endpoint and the core functionality. There's no unnecessary information, making it efficient. However, the structure could be slightly improved by combining the two sentences for better flow.

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's simplicity (0 parameters, 100% schema coverage, and an output schema exists), the description is adequate but minimal. It covers the basic purpose but lacks behavioral details that would be helpful for an agent, such as output format hints or usage context. The presence of an output schema reduces the need to describe return values, but more guidance on when to use this tool would enhance completeness.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. This aligns with the baseline expectation for zero-parameter tools.

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: 'List of all tokens along with basic info for each.' It specifies the verb ('List') and resource ('tokens'), and the HTTP method 'GET /api/emissions' reinforces this as a read operation. However, it doesn't explicitly differentiate from sibling tools like 'get_emission_data' or 'get_token_protocols', which might offer overlapping functionality.

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. It doesn't mention any prerequisites, exclusions, or comparisons to sibling tools such as 'get_emission_data' or 'get_token_protocols', leaving the agent to infer usage context based on the tool name alone.

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