Skip to main content
Glama
Sign In

Aether testnet wallet

by io.github.whoyoujoshin
OverviewDiscussionsAdmin

Get IBC inflow caps

get_inflow_caps
Read-onlyIdempotent

List the tokens other chains may send onto Aether over IBC, each with its channel, the cap on how much of it may be on Aether, how much is there now, how much is in flight back out and the room left. A transfer of any other token, or over the room, is refused and the sending chain refunds it: check the room before asking anyone to send USDC (or anything else) onto Aether. Read-only. active=false means this chain has no cap yet.

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_inflow_caps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
capsYes
activeYesfalse: this chain has no inflow cap yet and every token comes in uncapped
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only/idempotent/non-destructive, and the description goes beyond them by explaining the failure consequence — a transfer of another token or over the room is refused and refunded by the sending chain — and by decoding the active=false field. It does not state data freshness or how often caps update, which is the remaining gap.

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?

Front-loaded with what the list contains, then the consequence clause, then the actionable advice, then the field caveat. Dense but each clause carries information; the only waste is "Read-only," which merely restates readOnlyHint=true.

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?

Even though an output schema exists, the description summarizes the returned fields and explains the one non-obvious flag (active=false), plus the refusal/refund behavior on violation. Nothing an agent needs to call this correctly and interpret the result is missing.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param schema applies. The description instead spends its words on output semantics, which is the sensible allocation.

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?

Names a specific resource (IBC inflow caps per token) and enumerates exactly what each entry contains: channel, cap, current amount, in-flight amount, and remaining room. No sibling tool touches this data, so an agent can distinguish it immediately.

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?

Gives a concrete triggering condition: "check the room before asking anyone to send USDC (or anything else) onto Aether." No alternative tool is named, but none of the siblings overlap, so the lack of explicit exclusions is a minor gap rather than an ambiguity.

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

All Aether testnet wallet 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