Skip to main content
Glama

AINDEX

An agent's AINDEX fees and receipts

get_agent_fees
Read-only

AINDEX's fees on one agent: 0.025% of what it trades (Lighter and Robinhood Chain; on Lighter, Lighter's own 0.015% Plus fee comes on top, 0.04% a fill), a flat signing fee of 2 cents per Robinhood Chain transaction from credits, no deposit or withdrawal fee; anything owed, and the daily receipts with what each covered and paid. Needs the owner's access key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent": "<agent>"
    },
    "name": "get_agent_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, non-open-world call, so the bar is lower, and the description still adds real context: an auth requirement (owner's access key), the full fee model including which chains charge what, the source of the signing fee (credits), and the explicit absence of deposit/withdrawal fees. It also discloses the shape of the payload — what is owed plus daily receipts with what each covered and paid. It does not disclose whether the fee schedule is time-varying or how the returned window is bounded, which keeps it below a 5.

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?

It is a single front-loaded sentence whose first clause gives the purpose before the pricing detail. The nested parenthetical about Lighter's Plus fee stacking and "0.04% a fill" is dense and hard to parse on first read, and that arithmetic is arguably reference material rather than selection guidance. Still, there is no filler or redundant restatement of the title.

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?

With no output schema, the description must convey return values, and it does so partially by naming both the amount owed and the daily receipts with their coverage and payment figures. Fee rates are explained in unusual depth, but the retrieval window (days, its default and maximum) is never addressed, leaving a real gap for a tool whose return set is time-bounded. Adequate for a two-parameter read, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does not. The word "daily" only hints that the window controls receipt granularity; nothing states the 1–60 range, the 14-day default, or that the parameter bounds the receipts. The agent parameter's required p_… id format is never described either, though "one agent" weakly signals it.

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 opening clause names the resource and scope precisely: "AINDEX's fees on one agent" plus the receipts, so an agent knows it retrieves a fee breakdown and per-day receipt records for a single agent. It is clear without needing sibling differentiation, since no sibling in the list covers fees. The detail that follows is price arithmetic rather than purpose, so the core verb/resource statement is carried by the first few words.

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?

Usage is only implied: an agent infers it should call this to see what it owes or to reconcile past receipts. The one explicit prerequisite is "Needs the owner's access key," which is genuinely useful for call setup. There is no statement of when not to use it, no mention of how it relates to funding or balance tools, and no mention of the drift between the fee schedule and receipts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources