Skip to main content
Glama

Crypto Intelligence Statistics

crypto_stats

Retrieve statistics on crypto intelligence signals, executions, active networks, protocols, and date range via a free endpoint.

Instructions

Get statistics about the crypto intelligence dataset: total signals, total executions, networks and protocols active, date range. Free endpoint. Source: Liquidationbot multi-chain telemetry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for the 'crypto_stats' tool. It calls apiGet to fetch data from '/api/v1/crypto/stats' and returns the JSON response. No input parameters are required (empty inputSchema).
      async () => {
        const res = await apiGet<CryptoStatsResponse>("/api/v1/crypto/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • Registration of the 'crypto_stats' tool using server.registerTool() with the name 'crypto_stats', a description, an empty inputSchema, and the handler function.
    server.registerTool(
      "crypto_stats",
      {
        title: "Crypto Intelligence Statistics",
        description:
          "Get statistics about the crypto intelligence dataset: total signals, " +
          "total executions, networks and protocols active, date range. Free endpoint. " +
          "Source: Liquidationbot multi-chain telemetry.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<CryptoStatsResponse>("/api/v1/crypto/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • The TypeScript interface CryptoStatsResponse defines the response shape: dataset, source, update_frequency, networks, products, and stats.
    interface CryptoStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      networks: string[];
      products: string[];
      stats: Record<string, unknown>;
    }
  • The apiGet helper function used by the handler to make HTTP GET requests to the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that the tool is free and the data source (Liquidationbot multi-chain telemetry), which adds behavioral context. However, it omits details like update frequency, caching, or error behavior, leaving gaps for the agent.

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 two sentences with no redundant information. It front-loads the purpose and includes essential details (metrics list, free, source). Every word earns its place, achieving high conciseness.

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

Completeness4/5

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

Given zero parameters and no output schema, the description provides a solid overview of what the tool returns. It lists the core metrics and mentions the data source. It could be slightly more complete by indicating the output format, but the listed metrics give sufficient context for an agent to understand the tool's value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and the schema coverage is 100% (empty object). Per guidelines, baseline is 3. The description does not need to add parameter information, but it also does not clarify any implicit inputs that might be expected.

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 retrieves statistics about the crypto intelligence dataset, listing specific metrics (total signals, executions, networks, protocols, date range). The verb 'Get' and explicit resource differentiate it from sibling stats tools like 'dex_stats' which focus on different domains.

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

Usage Guidelines3/5

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

The description mentions 'Free endpoint', implying no cost, but does not provide explicit guidance on when to use this tool vs. alternatives or any exclusions. The usage context is minimal, leaving the agent to infer applicability.

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/carrierone/verilexdata-mcp'

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