Skip to main content

Gloam

by io.github.cryptoduke01

Overview Discussions Admin

Networks and assets

gloam_networks

Read-onlyIdempotent

The networks Gloam runs on, mainnets first, with each vault (pool) address, each mainnet's private swap router, the assets you can deposit (on mainnet: USDC.e, pathUSD, USDT0 and OUSD on Tempo, USDG and GLOAM on Robinhood Chain; on testnet: OUSD and PathUSD on Tempo, USDG and ETH on Robinhood Chain), explorers, RPCs and the testnet faucets.

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is a static configuration catalogue (addresses, routers, RPCs, faucets), which tells the agent it is a lookup rather than a live query. It does not say whether values are cached, versioned, or how large the payload is.

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 sentence with no filler, and the primary noun ('The networks Gloam runs on, mainnets first') is front-loaded. However, the long comma-chained parenthetical of per-chain assets is hard to scan and largely repeats the enum descriptions, so it is not maximally efficient.

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 carries the burden of describing the return value, and it does so reasonably by listing the fields returned (vault addresses, routers, assets, explorers, RPCs, faucets). For a zero-required-parameter read-only reference tool that is close to sufficient; only the relationship to gloam_info is missing.

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 enum values are individually annotated with their networks and assets, so the schema does the heavy lifting. The description's own asset lists (USDC.e, pathUSD, USDT0, OUSD, USDG, GLOAM on mainnet) partially duplicate that and add no syntax or default behaviour beyond it. Baseline 3 applies.

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 names a specific resource (Gloam networks) and enumerates the concrete payload: vault/pool addresses, per-mainnet swap routers, depositable assets, explorers, RPCs and faucets. That is far more than a restatement of the title. It falls short of a 5 because it never distinguishes itself from the sibling gloam_info, leaving the agent unsure which reference tool to open.

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 explicit instruction on when to call this versus gloam_info, gloam_vault_stats or gloam_plan_deposit. Usage is only inferable from the noun phrase 'the networks Gloam runs on'. The only routing hint ('Leave out for every network') lives in the schema, not the description.

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