Skip to main content

Gloam

by io.github.cryptoduke01

Overview Discussions Admin

Create a payment request link

gloam_create_payment_request

Read-onlyIdempotent

Make a link that asks someone to pay your Gloam address privately. It opens Pay in the Gloam app with the address, amount, asset and note filled in; the payer checks and sends. The details ride after the # of the link, so the payer's browser never sends them to a server. Needs your public Gloam address (gloamr1.…), never a key.

Input Schema

Name	Required	Description	Default
`to`	Yes	Your Gloam address to be paid at, gloamr1.… (public; find it in the app under Receive).
`name`	No	Your name as the payer should see it (up to 40 characters).
`note`	No	A reference the payer sees, e.g. "Invoice 042" (up to 80 characters).
`asset`	No	Token symbol or address, e.g. USDG on Robinhood Chain, OUSD or PathUSD on Tempo. Default: the network's main stablecoin.
`amount`	No	Amount in whole units, e.g. "12.50". Leave out to let the payer choose.
`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).	robinhood

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)."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)."

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)."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)."

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)."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)."

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)."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)."

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)."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)."

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)."New value: +"Gloam network: \"tempo\" (Tempo Moderato testnet, private stablecoin payments) or \"robinhood\" (Robinhood Chain testnet)."

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)."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)."

changedInput schema / properties / network / enum

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

First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint/idempotent/non-destructive) by disclosing a real behavioral trait: the payload rides after the '#' so the payer's browser never transmits it to a server. It also states the security prerequisite — a public gloamr1… address, never a key — and describes the payer-side confirmation flow.

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 short sentences, front-loaded with what the tool produces, then the payer flow, then the privacy and credential requirements. No filler or repetition of the title.

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?

For a link-building tool with full schema coverage and no output schema, the description covers the essential mechanics and constraints. The only real gap is that it never states plainly that the tool returns the link URL as a string, which the agent must assume.

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 all six parameters are already documented by the schema, which sets the baseline at 3. The description reinforces that address, amount, asset and note populate the link, but adds nothing beyond the schema and doesn't mention 'name' or 'network' at all.

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 artifact: 'Make a link that asks someone to pay your Gloam address'. The output (a payment-request link) and the audience (a payer) are both named, and no sibling tool in the list produces links, so it is unambiguous.

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 implied by the framing (you want someone to pay you), but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives. It never mentions how this differs from, say, gloam_plan_deposit or gloam_connect_full_agent, leaving the agent to infer the boundary.

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