Skipo

Get fiat deposit instructions

get_deposit_instructions

Read-only

Read-only. Where to send a BANK TRANSFER to fund this account in CLP — the fiat counterpart of get_deposit_addresses, which covers crypto.

⚠️ THE TRANSFER MUST COME FROM A BANK ACCOUNT IN THE USER OWN NAME AND RUT. Skipo matches an incoming transfer to an account by the originator RUT the bank reports, and there is no reference code, no memo and no per-customer account number to fall back on. A transfer sent from anyone else's account — a company account for a personal balance, a partner, a friend, a payment processor — CANNOT be matched and is NOT credited; recovering it is a manual support case. Tell the user this BEFORE they transfer, every time. The RUT that has to match is the one on their own Skipo account; it is not returned by any tool.

Each entry has assetSymbol, accountHolder, accountHolderNationalId, bankName, accountType, accountNumber, accountEmail and mustMatchSenderNationalId. accountHolderNationalId is SKIPO’s RUT — the destination — not the RUT the money has to come from.

More than one account is returned and they are INTERCHANGEABLE: a deposit into any of them credits the same balance. Prefer the one at the user own bank — a same-bank transfer in Chile settles faster and costs less.

CLP only; there is no USD bank account. Crypto funding is get_deposit_addresses. Amounts are not here: minimumDeposit is on get_assets. Returns a bare list, not paginated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deposit_instructions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover readOnly/openWorld/non-destructive; the description adds the crucial operational trait: matching is done by the originator RUT reported by the bank, with no reference code, memo, or per-customer account number, so a third-party transfer cannot be credited and becomes a manual support case. It also clarifies that accountHolderNationalId is Skipo's RUT (destination), not the sender's, which is a real misread trap, and that multiple returned accounts are interchangeable.

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 'Read-only.' and organized into purpose, warning, return shape, and alternatives. The all-caps warning and 'tell the user this ... every time' repetition are slightly verbose but proportionate to the financial risk being communicated.

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?

Covers everything an agent needs: no parameters, no pagination ('returns a bare list'), no output schema so the field list is supplied inline, currency scope stated, and cross-references for crypto addresses and minimum amounts. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4. The description instead documents the returned entry fields (assetSymbol, accountHolder, bankName, accountType, accountNumber, accountEmail, mustMatchSenderNationalId), which compensates for the absent output schema.

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 resource ('Where to send a BANK TRANSFER to fund this account in CLP') and explicitly positions it against get_deposit_addresses ('the fiat counterpart ... which covers crypto'). An agent can distinguish it from every sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use: CLP fiat funding only, no USD bank account exists, crypto goes to get_deposit_addresses, minimumDeposit lives on get_assets. It also tells the agent to surface the sender-RUT requirement to the user before every transfer, and to prefer the account at the user's own bank for faster settlement.

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

All Skipo tools Inspect

Try in Browser

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

Need Help?