Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_hacks

Retrieve comprehensive data on all cryptocurrency hacks tracked in the dashboard to analyze security incidents and monitor vulnerabilities.

Instructions

GET /api/hacks

Overview of all hacks on our Hacks dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_hacks' MCP tool. Decorated with @mcp.tool() for automatic registration. Fetches overview of all hacks from DefiLlama API endpoint '/api/hacks' using the shared make_request helper and returns the JSON response as string.
    @mcp.tool()
    async def get_hacks() -> str:
        """GET /api/hacks
        
        Overview of all hacks on our Hacks dashboard.
        """
        result = await make_request('GET', '/api/hacks')
        return str(result)
  • Shared asynchronous HTTP request helper function used by the 'get_hacks' tool (and others) to interact with the DefiLlama Pro 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 the full burden. It states this is a GET operation (implying read-only) and returns an overview, but lacks details on permissions, rate limits, pagination, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 with the API endpoint and purpose. Both sentences are relevant, though the first sentence 'GET /api/hacks' is somewhat redundant with the tool name. Overall, it's efficient with minimal waste.

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 moderately complete. However, with no annotations and a read operation, it should ideally mention the scope (e.g., time range, data freshness) or format of the overview to better guide the agent.

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 the schema fully documents the absence of inputs. The description adds no parameter information, which is acceptable given no parameters exist. Baseline is 4 for 0 parameters, as no compensation is needed.

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 retrieves an 'Overview of all hacks on our Hacks dashboard' with the verb 'GET' and resource 'hacks'. It distinguishes from siblings by specifying the 'Hacks dashboard' context, though not explicitly contrasting with other tools. The purpose is specific but lacks explicit sibling differentiation.

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 is provided on when to use this tool versus alternatives. The description mentions the 'Hacks dashboard' context, but there are no explicit instructions on prerequisites, timing, or comparisons with sibling tools like 'get_forks' or 'get_raises' that might relate to security incidents.

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