Skip to main content
Glama

Tuatara Deposit Address

tuatara_deposit_address
Read-onlyIdempotent

Needs your api_key (register_agent, no key needed). The owner's dedicated Tuatara Hedge Fund deposit address — one per owner, used only for the fund, no application. Money that arrives there is subscribed automatically (terms in the response: fees, 14 days' notice redemption, accepted assets and chains, USDT on Ethereum mainnet recommended). An agent key with no linked owner gets the one-click approve link instead. Also returns where the deposit is now (waiting / seen / subscribed / converted). (needs your linked account's key)

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": {
      "api_key": "<api_key>"
    },
    "name": "tuatara_deposit_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour api_key from register_agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior: deposits are auto-subscribed, terms (fees, 14-day notice redemption, accepted assets and chains, USDT on Ethereum recommended) come back in the response, and a status lifecycle (waiting/seen/subscribed/converted) is returned. The only gap is what happens to funds if terms are declined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the terms/status detail earns its place, but the auth requirement is duplicated ('Needs your api_key (register_agent, no key needed)' and again '(needs your linked account's key)') and the parenthetical 'no key needed' is confusing as written. Trimming the repeated clauses would sharpen it.

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 does the work of explaining what comes back: the address, the subscription terms, and the deposit status. Combined with the auth prerequisites and the no-owner fallback, an agent has enough to call it correctly; only the sibling distinction is left unaddressed.

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?

Only one parameter and schema coverage is 100%, so the schema already documents api_key fully; the description merely adds provenance ('from register_agent') and repeats the linked-account requirement. Baseline 3 is appropriate — it adds little beyond the schema.

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 states a specific verb+resource: it returns the owner's dedicated Tuatara Hedge Fund deposit address, one per owner, fund-only. That is far more specific than the title. It misses the chance to differentiate from the sibling get_deposit_address, which is exactly the tool an agent might confuse it with.

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?

It implies when to use it — depositing into the fund, with money auto-subscribed — and explains the no-linked-owner fallback (a one-click approve link). However, it never explicitly says when NOT to use it or names the alternative get_deposit_address / link_owner_account, leaving the sibling routing to inference.

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