Sentio Connect

Track wallet address

add_wallet_address

Idempotent

Track a wallet address for this account, so every other tool (balances, portfolio value, DeFi positions) starts covering it. Accepts a 0x EVM address, a .eth ENS name (resolved to an address before saving) or a 64-hex Sui address. A wallet covers every supported chain of its kind — Ethereum, Optimism, BNB Chain, Monad, Base, Arbitrum, Avalanche for an EVM address or ENS name; Sui for a Sui address — and picks up newly supported chains automatically; the result lists them in chains. Idempotent: an address already tracked comes back as its existing entry, flagged alreadyTracked, instead of being duplicated.

Input Schema

Name	Required	Description	Default
`address`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`added`	Yes
`chains`	Yes
`family`	Yes
`address`	Yes
`ensName`	No
`createdAt`	Yes
`alreadyTracked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 28, 2026

removedInput schema / properties / chain

Removed value: -{
-  "description": "Chain id: 1 Ethereum, 56 BNB Chain, 8453 Base, 42161 Arbitrum, sui_mainnet Sui",
-  "oneOf": [
-    {
-      "enum": [
-        "1"
-      ],
-      "title": "Ethereum",
-      "type": "string"
-    },
-    {
-      "enum": [
-        "56"
-      ],
-      "title": "BNB Chain",
-      "type": "string"
-    },
-    {
-      "enum": [
-        "8453"
-      ],
-      "title": "Base",
-      "type": "string"
-    },
-    {
-      "enum": [
-        "42161"
-      ],
-      "title": "Arbitrum",
-      "type": "string"
-    },
-    {
-      "enum": [
-        "sui_mainnet"
-      ],
-      "title": "Sui",
-      "type": "string"
-    }
-  ],
-  "type": "string"
-}

addedOutput schema / properties / added
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / alreadyTracked
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / chains

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "chain": {
+        "type": "string"
+      },
+      "chainName": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "chain",
+      "chainName"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / createdAt
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / family

Added value: +{
+  "enum": [
+    "evm",
+    "sui"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / tracked

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "added": {
-        "type": "boolean"
-      },
-      "address": {
-        "type": "string"
-      },
-      "alreadyTracked": {
-        "type": "boolean"
-      },
-      "chain": {
-        "type": "string"
-      },
-      "chainName": {
-        "type": "string"
-      },
-      "createdAt": {
-        "type": "number"
-      },
-      "id": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "chain",
-      "address",
-      "createdAt",
-      "added",
-      "alreadyTracked",
-      "chainName"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[
-  "tracked",
-  "address"
-]New value: +[
+  "id",
+  "family",
+  "address",
+  "chains",
+  "createdAt",
+  "added",
+  "alreadyTracked"
+]

Changed9 schema fields changedOct 21, 2026

removedInput schema / properties / chain / default
```
Removed value: -"1"
```

removedOutput schema / properties / added

Removed value: -{
-  "type": "boolean"
-}

removedOutput schema / properties / alreadyTracked
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / chain

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / chainName
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / createdAt
```
Removed value: -{
-  "type": "number"
-}
```

removedOutput schema / properties / id

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / tracked

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "added": {
+        "type": "boolean"
+      },
+      "address": {
+        "type": "string"
+      },
+      "alreadyTracked": {
+        "type": "boolean"
+      },
+      "chain": {
+        "type": "string"
+      },
+      "chainName": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "number"
+      },
+      "id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "chain",
+      "address",
+      "createdAt",
+      "added",
+      "alreadyTracked",
+      "chainName"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "chain",
-  "address",
-  "createdAt",
-  "added",
-  "alreadyTracked",
-  "chainName"
-]New value: +[
+  "tracked",
+  "address"
+]

First observedOct 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare idempotentHint and destructiveHint=false, and the description adds real context beyond that: ENS names are resolved to an address before saving, a wallet fans out across all chains of its kind and picks up new ones automatically, and the response carries `chains` and an `alreadyTracked` flag for the duplicate case.

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?

Four sentences, each doing distinct work: purpose and effect, accepted formats, chain coverage, duplicate handling. The most decision-relevant information comes first and there is no filler.

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?

A one-parameter mutation tool with an output schema — the schema covers the return shape, yet the description still names the salient response fields (`chains`, `alreadyTracked`), so an agent knows what to expect without opening the output schema.

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

Parameters5/5

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

Schema description coverage is 0% and the schema only declares a bare string with maxLength 255, so the description carries the full burden — and it does, enumerating the three accepted forms (0x EVM address, .eth ENS name, 64-hex Sui address) and what each one expands to chain-wise.

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 (track) and resource (wallet address) and immediately explains the downstream effect on balances, portfolio value and DeFi position tools, which cleanly distinguishes it from list_wallet_addresses and remove_wallet_address.

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

Usage Guidelines4/5

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

The phrase 'so every other tool... starts covering it' gives an implicit ordering cue (add before querying), and the idempotency note tells the agent it is safe to re-add. It never states an explicit when-not condition or names remove_wallet_address as the counterpart, so it stops short of full routing guidance.

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

All Sentio Connect 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.