Skip to main content
Glama

Plan a stablecoin off-ramp

plan_offramp
Read-only

Plan turning USDT or USDC into USD, EUR, GBP or AED in a company bank account: the indicative market value of the amount, the network fee to move the tokens now, each payout rail for that currency with the date the money should arrive if sent now (weekends and holidays included), the rules to check in that currency, a checklist before the first withdrawal, and the next step (a link to ask Align for a quote, plus a sign-up link where Align's convert page for the pair offers one). Indicative information, not a quote or an offer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>",
      "currency": "<currency>"
    },
    "name": "plan_offramp"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
amountNoAmount of the token to convert (optional)
networkNoNetwork the tokens are on, e.g. tron, ethereum, solana, base (optional)
currencyYesCurrency the bank account receives
sendDateNoDay the conversion is made, YYYY-MM-DD between 2026-11-01 and 2027-12-31 (default today, UTC)
beforeCutoffNoWhether the payout leaves before the bank's cut-off that day (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful behavioral context beyond that: results are indicative rather than a quote or offer, arrival dates already account for weekends and holidays, and time-sensitive figures assume 'sent now'. It does not disclose data freshness, failure modes for unsupported pairs, or the sign-up/link behavior conditions in detail.

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 the core action and resource, and the colon-list structure makes the returned deliverables scannable. It is a single very long sentence, so the alternative note and disclaimer land far from the opening verb, but every listed item carries real information and nothing is padding.

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 and six parameters, the description has to carry the return-value burden, and it does so thoroughly by enumerating each field an agent will get back. Gaps remain around the beforeCutoff parameter and what happens for unsupported token/currency or network combinations, which matters for a tool whose results are explicitly indicative.

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 83%, so the schema already documents token, currency, amount, network and sendDate. The description adds only marginal meaning, tying amount to 'indicative market value' and 'sent now' to the default sendDate; it says nothing about the beforeCutoff toggle or the sendDate date-range constraint.

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 verb ('Plan turning') and specific resource ('USDT or USDC into USD, EUR, GBP or AED in a company bank account'), then enumerates the exact deliverables (indicative value, network fee, payout rails with arrival dates, rules, checklist, quote link). That enumerated bundle distinguishes it from single-purpose siblings such as stablecoin_rate or stablecoin_network_fees without needing to name them.

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?

The framing 'before the first withdrawal' and 'the next step (a link to ask Align for a quote)' imply usage context in the off-ramp flow, and the closing 'Indicative information, not a quote or an offer' sets an expectation boundary. However, there is no explicit statement of when to call this versus alternatives like stablecoin_rate, nor any exclusion or precondition guidance beyond the generic disclaimer.

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.

Resources