Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_raises

Retrieve comprehensive data on all cryptocurrency fundraising rounds from the REI Crypto MCP Server's dashboard for investment analysis and market research.

Instructions

GET /api/raises

Overview of all raises on our Raises dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'get_raises' tool. Decorated with @mcp.tool() for registration. Fetches data from DefiLlama API /api/raises using the shared make_request helper and returns it as a string.
    @mcp.tool()
    async def get_raises() -> str:
        """GET /api/raises
        
        Overview of all raises on our Raises dashboard.
        """
        result = await make_request('GET', '/api/raises')
        return str(result)
  • The @mcp.tool() decorator registers the get_raises function as an MCP tool.
    @mcp.tool()
  • Shared helper function used by get_raises (and other tools) to make HTTP requests to the DefiLlama API.
    async def make_request(method: str, endpoint: str, params: Optional[Dict[str, Any]] = None) -> Any:
        """Make a request to the DefiLlama API."""
        try:
            response = await client.request(method, endpoint, params=params)
            response.raise_for_status()
            return response.json()
        except Exception as e:
            return f"Error: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'GET /api/raises' which implies a read-only HTTP GET operation, but doesn't disclose any behavioral traits like rate limits, authentication requirements, pagination, data freshness, or what happens if no raises exist. The description is minimal and lacks behavioral context.

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 with two sentences. The first sentence provides the API endpoint, and the second explains the purpose. No wasted words, though it could be more informative. The structure is front-loaded with the endpoint information.

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, for a data retrieval tool with no annotations, it lacks important context about what 'raises' means, the data format, or usage constraints. The output schema will handle return values, but the description should provide more operational context.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't discuss parameters, which is appropriate. Baseline for 0 parameters with complete schema coverage is 4.

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

Purpose3/5

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

The description states 'Overview of all raises on our Raises dashboard' which provides a general purpose (retrieving raise data) but lacks specificity about what 'raises' means or what data is included. It distinguishes from siblings by mentioning 'raises' but doesn't clarify if this is about fundraising, price increases, or other types of raises.

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?

No guidance on when to use this tool versus alternatives. The description mentions 'Raises dashboard' which implies a specific context, but doesn't explain when this tool is appropriate versus other data retrieval tools in the sibling list. No explicit when/when-not statements or alternative tool references.

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