Skip to main content

Gloam

by io.github.cryptoduke01

Overview Discussions Admin

Vault stats

gloam_vault_stats

Read-onlyIdempotent

Public totals for each Gloam vault, read from the chain: what it holds, and counts of deposits, private transfers, cash outs and payment messages. Totals only, no wallets. Cached about a minute.

Input Schema

Name	Required	Description	Default
`network`	No	Gloam network: "robinhood-mainnet" (Robinhood Chain mainnet: USDG and GLOAM), "tempo-mainnet" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), "base-mainnet" (Base mainnet: USDC, EURC, USDT, ETH), "ethereum-mainnet" (Ethereum mainnet: USDC, USDT, USDG, PYUSD, EURC, ETH), or a testnet: "tempo" (Tempo Moderato), "robinhood" (Robinhood Chain testnet), "base" (Base Sepolia) or "ethereum" (Ethereum Sepolia). Leave out for every network.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), or a testnet: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet), \"base\" (Base Sepolia) or \"ethereum\" (Ethereum Sepolia). Leave out for every network."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), \"base-mainnet\" (Base mainnet: USDC, EURC, USDT, ETH), \"ethereum-mainnet\" (Ethereum mainnet: USDC, USDT, USDG, PYUSD, EURC, ETH), or a testnet: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet), \"base\" (Base Sepolia) or \"ethereum\" (Ethereum Sepolia). Leave out for every network."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood",
-  "base",
-  "ethereum",
-  "robinhood-mainnet",
-  "tempo-mainnet"
-]New value: +[
+  "tempo",
+  "robinhood",
+  "base",
+  "ethereum",
+  "robinhood-mainnet",
+  "tempo-mainnet",
+  "base-mainnet",
+  "ethereum-mainnet"
+]

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), or a testnet: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet) or \"base\" (Base Sepolia). Leave out for every network."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), or a testnet: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet), \"base\" (Base Sepolia) or \"ethereum\" (Ethereum Sepolia). Leave out for every network."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood",
-  "base",
-  "robinhood-mainnet",
-  "tempo-mainnet"
-]New value: +[
+  "tempo",
+  "robinhood",
+  "base",
+  "ethereum",
+  "robinhood-mainnet",
+  "tempo-mainnet"
+]

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet) or \"base\" (Base Sepolia). Leave out for every network."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet: USDC.e, pathUSD, USDT0, OUSD), or a testnet: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet) or \"base\" (Base Sepolia). Leave out for every network."

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato) or \"robinhood\" (Robinhood Chain testnet). Leave out for every network."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato), \"robinhood\" (Robinhood Chain testnet) or \"base\" (Base Sepolia). Leave out for every network."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood",
-  "robinhood-mainnet",
-  "tempo-mainnet"
-]New value: +[
+  "tempo",
+  "robinhood",
+  "base",
+  "robinhood-mainnet",
+  "tempo-mainnet"
+]

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"tempo\" (Tempo Moderato testnet, private stablecoin payments) or \"robinhood\" (Robinhood Chain testnet). Leave out for both."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato) or \"robinhood\" (Robinhood Chain testnet). Leave out for every network."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood"
-]New value: +[
+  "tempo",
+  "robinhood",
+  "robinhood-mainnet",
+  "tempo-mainnet"
+]

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato) or \"robinhood\" (Robinhood Chain testnet). Leave out for every network."New value: +"Gloam network: \"tempo\" (Tempo Moderato testnet, private stablecoin payments) or \"robinhood\" (Robinhood Chain testnet). Leave out for both."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood",
-  "robinhood-mainnet",
-  "tempo-mainnet"
-]New value: +[
+  "tempo",
+  "robinhood"
+]

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / network / description

Previous value: -"Gloam network: \"tempo\" (Tempo Moderato testnet, private stablecoin payments) or \"robinhood\" (Robinhood Chain testnet). Leave out for both."New value: +"Gloam network: \"robinhood-mainnet\" (Robinhood Chain mainnet, real money: USDG and GLOAM), \"tempo-mainnet\" (Tempo mainnet, real money: USDC.e, pathUSD, USDT0, OUSD), or a testnet with play money: \"tempo\" (Tempo Moderato) or \"robinhood\" (Robinhood Chain testnet). Leave out for every network."

changedInput schema / properties / network / enum

Previous value: -[
-  "tempo",
-  "robinhood"
-]New value: +[
+  "tempo",
+  "robinhood",
+  "robinhood-mainnet",
+  "tempo-mainnet"
+]

First observedOct 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world access, so the safety profile is covered. The description adds genuinely new behavioral context: results are cached for about a minute (staleness expectation) and contain no wallet-level data (privacy/aggregation guarantee). It stops short of describing freshness on chain reorgs or the fetch cost, but the caching note is the most operationally relevant trait.

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?

Three tight sentences, zero filler, with the returned metrics front-loaded and the scope and caching caveats trailing. Every clause carries information an agent would otherwise have to guess.

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, the description does the work of naming the returned metrics and asserting the absence of wallet-level detail, plus a cache-freshness note. The only gap is the exact shape of the response (per-vault array vs. mapping) and whether totals are denominated in raw or USD terms, which an agent would still have to discover.

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% and the single 'network' parameter has a thorough enum description including which assets each network carries and the 'leave out for every network' default. The description adds nothing about the parameter, which is acceptable given the schema does the heavy lifting, so baseline 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?

States a specific resource (public vault totals read from chain) and enumerates exactly what is returned: holdings plus counts of deposits, private transfers, cash outs and payment messages. The scope exclusion 'Totals only, no wallets' cleanly separates it from any wallet-level or transaction-level sibling, so an agent can identify it without opening the schema.

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 'call this when you want aggregate vault metrics.' There is no explicit when-to-use, no statement of when not to use it, and no reference to any sibling alternative (e.g. gloam_info or gloam_networks for non-statistical context).

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

All Gloam tools Inspect

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