Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Cheapest Aquarium fee tank for a token

find_cheapest_fee_tank
Read-onlyIdempotent

Open Aquarium fee tanks that pay in a given token, cheapest first (by the datum price ratio), with the tank reference, owner and ADA inside.

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": {
      "token": "<token>"
    },
    "name": "find_cheapest_fee_tank"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tanks to return (1-25, default 5).
tokenYesToken ticker (USDM, FLDT, ...) or unit (policy id + asset name in hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds the sort key (datum price ratio) and the returned fields (tank reference, owner, ADA), which is useful, but says nothing about how ties or missing tanks are handled.

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?

A single front-loaded sentence that packs purpose, ordering, and return contents with no filler.

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?

For a read-only lookup with no output schema, the brief field list ('tank reference, owner and ADA') is minimally sufficient, but it omits pagination/limit behavior and what an empty result means, leaving gaps an agent would want covered.

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 coverage is 100%, so both parameters are already documented (limit range/default, token ticker-or-unit format). The description adds no syntax or format detail beyond the schema, warranting the baseline 3.

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?

States a specific verb and resource ('fee tanks that pay in a given token'), plus the ordering rule ('cheapest first, by the datum price ratio'). No sibling tool covers fee tanks, so an agent can route here unambiguously.

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 phrase 'that pay in a given token' implies the use case, but there is no explicit guidance on when to prefer this over get_aquarium_overview or a general token lookup, and no stated preconditions (e.g., token must exist).

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

All Realtap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources