get_deposit_addressRequires an API key. Get your account's dedicated on-chain deposit address and open networks to top up balance; only transfer to the listed networks and tokens.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / anyOfAdded value: +[
+ {
+ "allOf": [
+ {
+ "properties": {
+ "_truncated": {
+ "type": "boolean"
+ },
+ "address": {
+ "type": "string"
+ },
+ "bytes": {
+ "type": "integer"
+ },
+ "data": {},
+ "deposits_url": {
+ "type": "string"
+ },
+ "error": {
+ "type": "string"
+ },
+ "min_deposit_usd": {
+ "type": "string"
+ },
+ "networks": {
+ "items": {
+ "properties": {
+ "chain": {
+ "type": "string"
+ },
+ "chain_id": {
+ "type": "integer"
+ },
+ "explorer_tx_url": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "tokens": {
+ "items": {
+ "properties": {
+ "contract": {
+ "type": "string"
+ },
+ "decimals": {
+ "type": "integer"
+ },
+ "min_amount_raw": {
+ "type": "string"
+ },
+ "symbol": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "typical_credit_seconds": {
+ "type": "integer"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "not": {
+ "properties": {
+ "error": {
+ "const": "invalid_tool_arguments",
+ "type": "string"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+ }
+ ]
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "const": "invalid_tool_arguments",
+ "type": "string"
+ },
+ "message": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "reason": {
+ "enum": [
+ "invalid_root",
+ "schema_type",
+ "schema_enum",
+ "undeclared_property",
+ "credential_field",
+ "credential_value"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "error",
+ "reason",
+ "message"
+ ],
+ "type": "object"
+ }
+]Output schema / propertiesRemoved value: -{
- "_truncated": {
- "type": "boolean"
- },
- "address": {
- "type": "string"
- },
- "bytes": {
- "type": "integer"
- },
- "data": {},
- "deposits_url": {
- "type": "string"
- },
- "error": {
- "type": "string"
- },
- "min_deposit_usd": {
- "type": "string"
- },
- "networks": {
- "items": {
- "properties": {
- "chain": {
- "type": "string"
- },
- "chain_id": {
- "type": "integer"
- },
- "explorer_tx_url": {
- "type": "string"
- },
- "name": {
- "type": "string"
- },
- "tokens": {
- "items": {
- "properties": {
- "contract": {
- "type": "string"
- },
- "decimals": {
- "type": "integer"
- },
- "min_amount_raw": {
- "type": "string"
- },
- "symbol": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "typical_credit_seconds": {
- "type": "integer"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "status": {
- "type": "number"
- }
-}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: the API-key auth requirement and the constraint that only listed networks and tokens should receive transfers.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence with the auth prerequisite front-loaded and no filler. It is tight and front-loaded, though the semicolon-joined clause packs two ideas into one sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. The description covers auth, purpose, and the transfer caution. The only minor gap is the absence of any routing guidance among the many sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. No syntax or format details are needed, and none are missing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (account's dedicated on-chain deposit address and open networks) with the purpose (to top up balance). An agent can distinguish this from sibling inventory tools like list_chains or get_account without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context ('to top up balance') and adds a warning about transferring only to listed networks and tokens, but it never states when to use this versus alternatives such as list_chains or get_account. Usage is inferable rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.