Skip to main content
Glama

get_summary

Read-onlyIdempotent

Retrieve a combined market summary for any cryptocurrency coin, including mark price, oracle price, funding rate, open interest, 24h volume, and 24h liquidation volumes in a single call.

Instructions

Get combined market summary for a coin in a single call. Returns mark price, oracle price, funding rate, open interest, 24h volume, and 24h liquidation volumes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCoin/market symbol, e.g. 'BTC', 'ETH', 'SOL'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResult data object

Implementation Reference

  • src/index.ts:613-619 (registration)
    Registration of the 'get_summary' tool via registerCurrentTool helper. The handler delegates to api().hyperliquid.summary(coin) for a combined Hyperliquid market summary.
    registerCurrentTool(
      "get_summary",
      "Get combined market summary for a coin in a single call. Returns mark price, oracle price, funding rate, open interest, 24h volume, and 24h liquidation volumes.",
      (coin) => api().hyperliquid.summary(coin),
      CoinParam,
      normalizeHLCoin
    );
  • The registerCurrentTool helper function that wraps the actual handler logic for get_summary. It takes a coin parameter, normalizes it, calls the SDK's summary function, and formats the response using formatResponse with ObjectOutputSchema.
    // Pattern 2: Current snapshot (coin only)
    function registerCurrentTool(
      name: string,
      description: string,
      sdkCall: (coin: string) => Promise<unknown>,
      coinSchema: z.ZodString,
      normFn: (coin: string) => string
    ): void {
      registerTool(name, description, { coin: coinSchema }, ObjectOutputSchema, async (params) => {
        const data = await sdkCall(normFn(params.coin));
        return formatResponse(data);
      });
    }
  • Input schema (CoinParam) for the coin parameter used by get_summary tool.
    const CoinParam = z
      .string()
      .describe("Coin/market symbol, e.g. 'BTC', 'ETH', 'SOL'");
  • Output schema (ObjectOutputSchema) for get_summary, which returns a single result object.
    const ObjectOutputSchema: ZodRawShape = {
      data: z.record(z.unknown()).describe("Result data object"),
    };
Behavior4/5

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

Annotations already indicate a safe, read-only operation. The description adds value by detailing the returned data (mark price, oracle price, etc.), providing context beyond the annotations.

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?

Two sentences, front-loaded with the main purpose, followed by a concise list of fields. No unnecessary words.

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?

For a simple input with an output schema, the description lists the key return fields, providing sufficient context for an agent. Could mention output schema details, but that is covered by the schema itself.

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?

The single parameter 'coin' is fully described in the schema with examples. The description does not add new semantic meaning beyond what the schema provides (100% coverage).

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 it gets a 'combined market summary for a coin in a single call' and lists the specific returned fields, distinguishing it from sibling tools that return individual metrics (e.g., get_funding_current, get_open_interest).

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 implies it is a convenience for multiple fields but does not explicitly state when to use it versus alternatives or provide exclusions. Usage context is inferred but not stated.

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/0xArchiveIO/0xarchive-mcp'

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