Skip to main content
Glama
ironflowsh

Ironflow MCP

Official
by ironflowsh

get_fills

Retrieve trade fills for a wallet address, with optional market filtering and result limits. Track on-chain derivative trading activity.

Instructions

Get trade fills for a specific wallet address, optionally filtered by market

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesWallet address (e.g. 0x...)
marketNoOptional market filter — native HL (e.g. "BTC-PERP") or HIP-3 builder market "<issuer>:<base>-PERP" (e.g. "flx:GAS-PERP")
limitNoNumber of fills (1-100, default 20)

Implementation Reference

  • Handler for the 'get_fills' tool. Extracts 'address' (required), 'market' (optional), and 'limit' (optional, default 20) from args, calls api.getFills(), and returns JSON-stringified result.
    handler: async (args, api) => {
      const address = requireString(args, "address");
      const market = optionalString(args, "market", "");
      const limit = optionalNumber(args, "limit", 20);
      const data = await api.getFills(address, market, String(limit));
      return JSON.stringify(data, null, 2);
    },
  • Input schema for 'get_fills' tool, defining address (required string), market (optional string), and limit (optional number, default 20).
    inputSchema: {
      type: "object",
      properties: {
        address: { type: "string", description: "Wallet address (e.g. 0x...)" },
        market: { type: "string", description: 'Optional market filter — native HL (e.g. "BTC-PERP") or HIP-3 builder market "<issuer>:<base>-PERP" (e.g. "flx:GAS-PERP")' },
        limit: { type: "number", description: "Number of fills (1-100, default 20)" },
      },
      required: ["address"],
    },
  • src/tools.ts:242-261 (registration)
    Tool registration entry for 'get_fills' in the tools array. Contains name, description, inputSchema, and handler.
    {
      name: "get_fills",
      description: "Get trade fills for a specific wallet address, optionally filtered by market",
      inputSchema: {
        type: "object",
        properties: {
          address: { type: "string", description: "Wallet address (e.g. 0x...)" },
          market: { type: "string", description: 'Optional market filter — native HL (e.g. "BTC-PERP") or HIP-3 builder market "<issuer>:<base>-PERP" (e.g. "flx:GAS-PERP")' },
          limit: { type: "number", description: "Number of fills (1-100, default 20)" },
        },
        required: ["address"],
      },
      handler: async (args, api) => {
        const address = requireString(args, "address");
        const market = optionalString(args, "market", "");
        const limit = optionalNumber(args, "limit", 20);
        const data = await api.getFills(address, market, String(limit));
        return JSON.stringify(data, null, 2);
      },
    },
  • API helper method 'getFills' on the IronflowAPI class. Builds query params with address, limit, and optionally market, then GETs /v1/fills.
    async getFills(address: string, market: string = "", limit: string = "20"): Promise<unknown> {
      const params: Record<string, string> = { address, limit };
      if (market) params.market = market;
      return this.get("/v1/fills", params);
    }
Behavior2/5

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

No annotations provided; description only states basic read operation without disclosing data freshness, pagination behavior, or prerequisites like address existence.

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?

Single sentence, 14 words, no redundancy, directly conveys purpose.

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

Completeness2/5

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

Description does not explain what a fill is, output structure, or constraints like limit range, leaving gaps despite schema coverage.

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?

Schema covers 100% of parameters; description adds no extra meaning beyond what the schema already provides, so baseline of 3 applies.

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 retrieves trade fills for a specific wallet address with optional market filtering, using specific verb and resource, distinguishing it from siblings like get_recent_trades.

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 on when to use this tool versus alternatives (e.g., get_recent_trades), nor any exclusions or prerequisites.

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/ironflowsh/mcp'

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