Skip to main content
Glama

read_asset_manager_current

Read-onlyIdempotent

Read which asset managers are currently enabled on an account, with their decoded on-chain configuration. Returns the active managers (address, protocol, initiator, decoded strategy metadata, slippage and value-loss caps, fee recipient), the intents they map to, and Merkl claim state including whether reward tokens still need registering. Managers from superseded deployments are listed separately under deprecated: pass their addresses to write_account_automations_delta to clear them, or run write_account_automations which disables them as part of the save. A deprecated cow_swapper no longer swaps: a delta apply moves the account to the current CowSwapper and keeps its auto-swap target (buy token, sell tokens); a save keeps it only when its intents restate that target from the deprecated entry's metadata. read_ok is false when chain state could not be read, in which case the result is unreliable rather than empty.

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": {
      "account_address": "<account_address>"
    },
    "name": "read_asset_manager_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
chain_idNoChain ID: 8453 (Base), 130 (Unichain), 10 (Optimism), or 4663 (Robinhood)
account_addressYesArcadia account address

Output Schema

NameRequiredDescriptionDefault
merklNo
accountYes
enabledYes
read_okYes
chain_idYes
warningsYes
deprecatedYes
inferred_intentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain_id / description
      Previous value: -"Chain id: 8453 Base, 130 Unichain, 10 Optimism"New value: +"Chain ID: 8453 (Base), 130 (Unichain), 10 (Optimism), or 4663 (Robinhood)"
  2. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / properties / deprecated / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / enabled / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / merkl / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent hints, it discloses the exact return shape categories (address, protocol, initiator, strategy metadata, caps, fee recipient), that deprecated managers are segregated, and the critical failure semantic that read_ok=false means unreliable rather than empty. It also explains the downstream consequence of deprecation (cow_swapper no longer swaps) which is behavior an agent could not infer from annotations.

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?

The purpose and return contents are front-loaded in the first two clauses, and the dense migration rules come after. The cow_swapper paragraph is long and bordering on write-tool documentation, but it earns its place for an agent deciding whether to clear deprecated entries.

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 an output schema present the description need not restate return fields, yet it still covers the failure mode and the deprecated bucket, making it safe to invoke. The only gap is that it never states whether the read is chain-scoped by the chain_id parameter explicitly, though the schema handles that.

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 100%, so both chain_id (with its enumerated chain list) and account_address are fully documented in the schema. The description adds no format, default, or constraint detail beyond that, so the baseline 3 applies.

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 first sentence names a specific verb ('Read') and resource ('asset managers currently enabled on an account') plus the decoded-configuration scope, which is concrete enough to separate it from siblings like read_asset_manager_intents. It stops short of explicitly contrasting with that closest read sibling, so it is clear but not fully differentiated.

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?

It names two concrete follow-up alternatives (write_account_automations_delta for targeted clearing, write_account_automations for bulk disabling) and the condition that selects each. What is missing is guidance on when to call this read in the first place versus read_asset_manager_intents.

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.