Skip to main content
Glama

read_asset_manager_intents

Read-onlyIdempotent

List the automation intents Arcadia supports, with the parameters each one accepts. Pass account_address to also get per-account availability: which intents can be enabled right now and, for any that cannot, the compatibility rule blocking it. Pass position_id as well to scope availability to one LP position. Without account_address this returns the catalog only.

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": "read_asset_manager_intents"
  }
}

Input Schema

NameRequiredDescriptionDefault
chain_idNoChain ID: 8453 (Base), 130 (Unichain), 10 (Optimism), or 4663 (Robinhood)
position_idNoLP position (NFT) id to scope availability to. Requires account_address.
account_addressNoArcadia account address. Include it to get live per-account availability.

Output Schema

NameRequiredDescriptionDefault
usageYes
automationsYes
shared_paramsYes
availability_errorNo

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
    • addedInput schema / properties / position_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / position_id / minimum
      Added value: +-9007199254740991
    • 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 / automations / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / account_address
      Added value: +{
      +  "description": "Arcadia account address. Include it to get live per-account availability.",
      +  "type": "string"
      +}
    • addedInput schema / properties / chain_id / default
      Added value: +8453
    • changedInput schema / properties / chain_id / description
      Previous value: -"Filter to automations available on this chain. Omit to see all."New value: +"Chain id: 8453 Base, 130 Unichain, 10 Optimism"
    • addedInput schema / properties / position_id
      Added value: +{
      +  "description": "LP position (NFT) id to scope availability to. Requires account_address.",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / availability_error
      Added value: +{
      +  "type": "string"
      +}
  4. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: that availability includes which intents can be enabled right now and the compatibility rule blocking the rest, which is non-obvious output semantics. It stops short of mentioning any rate limits or auth requirements.

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 short sentences, front-loaded with the core purpose and then the two opt-in modes in the order an agent would consider them. Every clause carries information about scope or return content; nothing is redundant with the title or annotations.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains the three distinct response modes. For a zero-required-parameter, read-only catalog tool this covers everything an agent needs to choose parameters and interpret results.

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?

Schema description coverage is already 100%, so the baseline is 3. The description still adds value by tying account_address to a changed response shape (catalog versus live availability) and by reinforcing the position_id-requires-account_address dependency, which makes the conditional relationship clearer than the schema alone.

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 ('List the automation intents Arcadia supports') and immediately extends it with 'the parameters each one accepts,' so the agent knows both the catalog and its payload shape. The last sentence delineates the default mode from the availability modes, which separates it from the write_account_automations siblings.

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?

Gives explicit conditional guidance: pass account_address for live per-account availability, pass position_id as well to scope to a single LP position, and 'Without account_address this returns the catalog only' defines the no-argument default. The agent can pick the right call shape without inspecting the schema.

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.