Skip to main content
Glama

hyperd.pricing.get

Retrieve current USDC pricing for hyperD paid endpoints on Base. Free access without a wallet.

Instructions

Get the current price list for all hyperD paid endpoints (in USDC on Base). FREE — no wallet required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:177-182 (registration)
    Registration of the 'hyperd.pricing.get' tool on the MCP server. It has no input schema (empty {}), a description, and calls freeGet('/api/pricing') as its handler.
    server.tool(
      "hyperd.pricing.get",
      "Get the current price list for all hyperD paid endpoints (in USDC on Base). FREE — no wallet required.",
      {},
      async () => asText(await freeGet("/api/pricing")),
    );
  • The 'freeGet' helper function is the actual handler used by hyperd.pricing.get. It makes a GET request to the API_BASE + path, formats query params, and returns JSON. Since hyperd.pricing.get is a free tool, it delegates to this function.
    async function freeGet(
      path: string,
      query: Record<string, string | number | boolean | undefined> = {},
    ): Promise<unknown> {
      const url = new URL(`${API_BASE}${path}`);
      for (const [k, v] of Object.entries(query)) {
        if (v !== undefined && v !== "" && v !== null) url.searchParams.set(k, String(v));
      }
      const r = await fetch(url);
      if (!r.ok) {
        throw new Error(`HTTP ${r.status} on free request: ${await r.text()}`);
      }
      return r.json();
    }
  • The 'asText' helper wraps the JSON response into the MCP content format (text type). Used by all tool handlers including hyperd.pricing.get.
    function asText(data: unknown) {
      return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for hyperd.pricing.get — empty object (no input parameters required). The free pricing tool takes no arguments.
    {},
Behavior3/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 discloses that the tool is free and requires no wallet, but does not mention error handling, rate limits, or idempotency.

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, short sentence followed by a brief note. It is front-loaded with the action and has no unnecessary words.

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

Completeness5/5

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

Given the tool has no parameters, no output schema, and no annotations, the description provides all essential information: what it does, the currency, network, and accessibility. Suitable for a simple getter.

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 zero parameters, and schema coverage is 100%. According to guidelines, baseline score is 4 when there are no parameters.

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 the current price list for hyperD paid endpoints, specifying the currency (USDC) and network (Base). This distinguishes it from sibling tools like hyperd.balance.get or hyperd.dex.quote.

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

Usage Guidelines4/5

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

The description mentions it is free and requires no wallet, which implies ease of use. However, it does not explicitly state when to use this tool versus alternatives or provide any exclusions.

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/hyperd-ai/hyperd-mcp'

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