Skip to main content
Glama

Plan a private deposit

gloam_plan_deposit
Read-onlyIdempotent

Plan a deposit into a private Gloam balance (a shield): the steps, what becomes public and what stays private, and the app link to do it. Does not sign or send anything; you sign in your own wallet in the app.

Input Schema

NameRequiredDescriptionDefault
assetNoToken symbol or address. Default: the network's main stablecoin (OUSD on Tempo, USDG on Robinhood Chain).
amountNoAmount in whole units, e.g. "25".
networkNoGloam 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).tempo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +]
  2. Changed2 schema fields changed
    • 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"
      +]
  3. Changed1 schema field changed
    • 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)."
  4. Changed2 schema fields changed
    • 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"
      +]
  5. Changed2 schema fields changed
    • 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"
      +]
  6. Changed2 schema fields changed
    • 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"
      +]
  7. Changed2 schema fields changed
    • 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"
      +]
  8. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare readOnlyHint/idempotent/non-destructive, and the description adds the crucial clarification that despite 'deposit' nothing is signed or broadcast — the user signs in their own wallet in the app. It also discloses the return content (steps, privacy breakdown, app link), resolving the main behavioral doubt an agent would have.

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?

Two clauses, zero filler, with the action and object front-loaded and the non-execution caveat immediately after. Every phrase carries information.

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?

For a 3-param, no-output-schema planning tool with full annotation coverage, the description supplies the two things structured fields can't: what the plan returns and that no transaction occurs. Nothing an agent needs to call it correctly 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 coverage is 100% and the schema fully documents asset (including per-network default), amount format, and the network enum with token lists. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work.

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 (plan) and resource (deposit into a private Gloam balance / shield), and even enumerates what the response contains: steps, the public/private split, and an app link. No sibling tool covers deposit planning, so an agent can route here without ambiguity.

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 — 'plan a deposit' plus the note that signing happens in the user's own wallet establishes this as the pre-execution step. But no alternative is named and no explicit when-not condition or prerequisite (e.g., connect first, check network support via gloam_networks) is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.