Skip to main content
Glama

Executed pieces

get_fills

Retrieve executed order fills to inspect USDG spent, tokens received, the fresh receiving address, and the transaction link.

Instructions

Shows executed pieces: USDG spent, tokens received, the fresh address holding them, and the transaction link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fills"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdNoLimit to one order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the returned data shape (spend amount, received tokens, the 'fresh' address holding them, transaction link), which usefully implies a read-only lookup and reveals that funds land on a newly generated address. It says nothing about ordering, pagination, limits, or what an empty result means for a one-to-many relationship between orders and fills.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a clear verb and an enumerated field list; nothing is padded. The enumerated fields are informative rather than redundant, though the phrase 'executed pieces' echoes the title rather than using the more conventional 'fills' terminology.

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?

With no output schema and no annotations, the description partially compensates by describing what the response contains, and with only one fully documented optional parameter the schema burden is light. Gaps remain around result set behavior (all fills vs. filtered, ordering, volume) but the tool is simple enough that these are minor.

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 description coverage is 100% and the single optional parameter is documented in the schema as 'Limit to one order'. The description adds no meaning beyond that, which is acceptable given full schema coverage, but it also fails to clarify whether omitting orderId returns all fills or is an error condition.

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 uses a concrete verb ('Shows') and names the resource ('executed pieces') plus the specific fields returned (USDG spent, tokens received, holding address, transaction link). It does not, however, distinguish itself from siblings such as get_orders, so an agent must infer that this is the execution-level view rather than the order-level one.

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?

There is no when-to-use guidance: nothing says to call this after placing or routing an order, or how it differs from get_orders or route_order. The optional orderId filter is not mentioned either, so the agent gets no signal about when to scope the call to a single order versus fetching everything.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.