Skip to main content
Glama

get_24h_volume

Retrieve the 24-hour trading volume data on SailFish DEX using the EDUCHAIN Agent Kit for precise market insights and analysis.

Instructions

Get the 24-hour trading volume on SailFish DEX

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_24h_volume': calls subgraph.get24HVolume() and returns JSON response with volumeUSD.
    case 'get_24h_volume': {
      const volume = await subgraph.get24HVolume();
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({ volumeUSD: volume }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:255-262 (registration)
    Tool registration in ListTools handler, including name, description, and input schema (no parameters required).
      name: 'get_24h_volume',
      description: 'Get the 24-hour trading volume on SailFish DEX',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Helper function get24HVolume() that fetches factory from subgraph and returns totalVolumeUSD as proxy for 24h volume.
    export async function get24HVolume(): Promise<string> {
      try {
        const factory = await getFactory();
        if (!factory) {
          throw new Error('Factory data not available');
        }
        
        // Note: This is a simplified approach. For more accurate 24h volume,
        // you would need to compare current volume with volume from 24h ago
        return factory.totalVolumeUSD;
      } catch (error) {
        console.error('Error calculating 24h volume:', error);
        throw error;
      }
    }
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 states the tool retrieves data ('Get'), implying it's a read operation, but doesn't specify whether it requires authentication, has rate limits, returns real-time or cached data, or what the output format is. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, clear sentence: 'Get the 24-hour trading volume on SailFish DEX'. It's front-loaded with the core purpose, has no unnecessary words, and efficiently conveys the essential information without 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's simplicity (0 parameters, no annotations, no output schema), the description is adequate but incomplete. It states what the tool does but lacks details on behavioral aspects like data freshness, error handling, or output structure. For a read-only tool in a DEX context, more context on what '24-hour trading volume' entails (e.g., aggregated, per-pool) 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 tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description doesn't add parameter semantics, but this is appropriate given the lack of parameters, warranting a baseline high score as it doesn't mislead or omit necessary information.

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: 'Get the 24-hour trading volume on SailFish DEX'. It specifies the verb ('Get'), resource ('24-hour trading volume'), and context ('on SailFish DEX'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from siblings like 'get_pool_historical_data' or 'get_token_historical_data', which might also provide volume-related data, so it doesn't reach a perfect score.

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 prerequisites, exclusions, or compare it to siblings such as 'get_pool_historical_data' or 'get_token_historical_data', which could offer overlapping functionality. This leaves the agent without clear usage context.

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

Related 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/SailFish-Finance/educhain-ai-agent-kit'

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