Skip to main content
Glama

read.strategy.info

Read-onlyIdempotent

Retrieve APY per range width, pool info, and configuration for a concentrated liquidity strategy by ID.

Instructions

Get full detail for a specific LP strategy by ID — includes APY per range width (narrower range = higher APY but more rebalancing cost/risk), pool info, and configuration. Use read.strategy.list to discover strategy IDs. All APY values are decimal fractions (1.0 = 100%, 0.05 = 5%).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategy_idYesStrategy ID
chain_idNoChain ID: 8453 (Base), 130 (Unichain), or 10 (Optimism)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for read.strategy.info tool. Calls api.getStrategyInfo(chain_id, strategy_id) and returns the full strategy detail including APY per range width, pool info, and configuration.
    async ({ strategy_id, chain_id }) => {
      try {
        const result = await api.getStrategyInfo(chain_id, strategy_id);
        return {
          content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
          structuredContent: result as Record<string, unknown>,
        };
      } catch (err) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error: ${err instanceof Error ? err.message : String(err)}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Registration of read.strategy.info tool with title 'Get Strategy Info', input schema (strategy_id: number, chain_id: number with default 8453), output schema (StrategyDetailOutput), and annotations (readOnlyHint, idempotentHint).
    server.registerTool(
      "read.strategy.info",
      {
        annotations: {
          title: "Get Strategy Info",
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
        description:
          "Get full detail for a specific LP strategy by ID — includes APY per range width (narrower range = higher APY but more rebalancing cost/risk), pool info, and configuration. Use read.strategy.list to discover strategy IDs. All APY values are decimal fractions (1.0 = 100%, 0.05 = 5%).",
        inputSchema: {
          strategy_id: z.number().describe("Strategy ID"),
          chain_id: z.number().default(8453).describe(CHAIN_ID_DESCRIPTION),
        },
        outputSchema: StrategyDetailOutput,
      },
      async ({ strategy_id, chain_id }) => {
        try {
          const result = await api.getStrategyInfo(chain_id, strategy_id);
          return {
            content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            structuredContent: result as Record<string, unknown>,
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • Import and registration call for registerStrategyTools which registers read.strategy.info (and list/recommendation).
    import { registerStrategyTools } from "./read/strategy.js";
    import { registerPointsTools } from "./read/points.js";
    import { registerGuideTools } from "./read/guides.js";
    import { registerWalletTools } from "./read/wallet.js";
    import { registerAssetManagerTools } from "./read/asset-managers.js";
    import { registerCreateTool } from "./write/account/create.js";
    import { registerDepositTool } from "./write/account/deposit.js";
    import { registerWithdrawTool } from "./write/account/withdraw.js";
    import { registerBorrowTool } from "./write/account/borrow.js";
    import { registerRepayTool } from "./write/account/repay.js";
    import { registerApproveTool } from "./write/wallet/approve.js";
    import { registerPoolDepositTool } from "./write/pool/deposit.js";
    import { registerPoolRedeemTool } from "./write/pool/redeem.js";
    import { registerRebalancerTool } from "./write/asset-managers/rebalancer.js";
    import { registerCompounderTools } from "./write/asset-managers/compounder.js";
    import { registerYieldClaimerTools } from "./write/asset-managers/yield-claimer.js";
    import { registerCowSwapperTool } from "./write/asset-managers/cow-swapper.js";
    import { registerMerklOperatorTool } from "./write/asset-managers/merkl-operator.js";
    import { registerSetAssetManagersTool } from "./write/asset-managers/set-asset-managers.js";
    import { registerSendTool } from "./dev/send.js";
    import { registerAddLiquidityTool } from "./write/account/add-liquidity.js";
    import { registerRemoveLiquidityTool } from "./write/account/remove-liquidity.js";
    import { registerSwapTool } from "./write/account/swap.js";
    import { registerDeleverageTool } from "./write/account/deleverage.js";
    import { registerStakeTool } from "./write/account/stake.js";
    import { registerCloseTool } from "./write/account/close.js";
    
    export function registerAllTools(
      server: McpServer,
      api: ArcadiaApiClient,
      chains: Record<ChainId, ChainConfig>,
    ) {
      // Read tools
      registerAccountTools(server, api, chains);
      registerPoolTools(server, api);
      registerAssetTools(server, api);
      registerStrategyTools(server, api);
  • Output schema for StrategyDetailOutput - passthrough object (accepts any response shape).
    export const StrategyDetailOutput = z.object({}).passthrough();
  • API client method getStrategyInfo that calls GET /strategies/{strategyId}/info with chain_id query parameter.
    async getStrategyInfo(chainId: number, strategyId: number) {
      return this.get(`/strategies/${strategyId}/info`, { chain_id: chainId });
    }
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint, covering safety and idempotency. Description adds valuable context about APY values being decimal fractions, which aids correct interpretation of output.

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?

Two concise sentences cover purpose, contents, usage tip, and important decimal clarification. No extraneous text; front-loaded with essential information.

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?

Given the presence of an output schema, the description sufficiently covers purpose, input semantics, and a key output detail (decimal format). It also connects to the sibling tool for ID discovery, making it complete for an agent to use correctly.

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 description coverage is 100%; both parameters have adequate descriptions. The tool description reinforces strategy_id but adds no new semantic information beyond the schema.

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?

The description clearly states the tool retrieves full details for a specific LP strategy by ID, listing included elements (APY per range width, pool info, configuration). It differentiates from sibling read.strategy.list by noting that tool is for discovering IDs.

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?

Explicitly instructs to use read.strategy.list to discover strategy IDs, providing clear guidance on prerequisite and sibling tool usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arcadia-finance/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server