Skip to main content
Glama

read.guides

Read-onlyIdempotent

Retrieve workflow guides for Arcadia addresses, automation setup, strategy templates, and pool evaluation. Use before multi-step LP management tasks.

Instructions

Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (rebalancer/compounder setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNooverview = addresses + tool catalog, automation = rebalancer/compounder/claimer setup, strategies = step-by-step LP templates, selection = pool evaluation + leverage sizing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes
contentYes

Implementation Reference

  • The async handler function that executes the tool logic for 'read.guides'. It receives a topic, retrieves the guide content from a pre-loaded Map, and returns it as structured content.
        async ({ topic }) => {
          if (!topic) {
            const topicList = Object.entries(TOPICS)
              .map(([key, { summary }]) => `  ${key}: ${summary}`)
              .join("\n");
            const result = {
              topic: "",
              content: `topic is required. Valid topics:\n${topicList}`,
            };
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
              structuredContent: result,
              isError: true,
            };
          }
          const result = { topic, content: guides.get(topic)! };
          return {
            content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            structuredContent: result,
          };
        },
      );
    }
  • The tool registration call including the input schema (zod enum of topic keys) and output schema (GuideOutput). The tool name 'read.guides' is registered here.
    server.registerTool(
      "read.guides",
      {
        annotations: {
          title: "Get Guide",
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
        description:
          "Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (rebalancer/compounder setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).",
        inputSchema: {
          topic: z
            .enum(TOPIC_KEYS)
            .optional()
            .describe(
              "overview = addresses + tool catalog, automation = rebalancer/compounder/claimer setup, strategies = step-by-step LP templates, selection = pool evaluation + leverage sizing",
            ),
        },
        outputSchema: GuideOutput,
      },
  • Where registerGuideTools(server) is called to register the tool on the MCP server.
    registerGuideTools(server);
  • The TOPICS constant defining available guide topics (overview, automation, strategies, selection) and their corresponding file paths and summaries.
    const TOPICS = {
      overview: {
        file: "SKILL.md",
        summary:
          "Tool catalog, token/contract/lending pool addresses, asset manager addresses, account versions",
      },
      automation: {
        file: "automation.md",
        summary:
          "Rebalancer, compounder, yield claimer, merkl operator, CoW swapper setup and addresses",
      },
      strategies: {
        file: "strategies.md",
        summary:
          "Step-by-step strategy templates: delta neutral leveraged LP, protocol owned liquidity, closing sequences",
      },
      selection: {
        file: "selection.md",
        summary:
          "Strategy evaluation framework: pool selection, range width, leverage sizing, automation combos, exit signals",
      },
    } as const;
  • The GuideOutput zod schema defining the output shape: topic (string) and content (string).
    export const GuideOutput = z.object({
      topic: z.string(),
      content: z.string(),
    });
Behavior4/5

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

Annotations already mark the tool as read-only and idempotent. The description adds behavioral context by stating it returns guides and reference documentation, and enumerates the content of each topic. It does not contradict annotations and provides extra detail on what the user will receive.

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 sentences with no filler. The first sentence covers purpose and timing, the second lists topics. Every word adds value; it is both concise and clearly structured.

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?

For a simple tool with one enum parameter and an output schema, the description is complete. It explains the tool's purpose, usage context, and available topics. No additional information is needed.

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?

The only parameter 'topic' is fully documented in the schema with an enum and description. The description repeats the enum values and adds brief explanations. Since schema coverage is 100%, the description adds marginal value 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 identifies the tool as a documentation resource for Arcadia workflow guides and reference. It specifies when to use it (before multi-step workflows) and lists the exact topics available. It is easily distinguished from siblings which are operational read/write tools.

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?

Explicitly states when to call: before multi-step workflows like opening LP positions, enabling automation, or closing positions. It also provides scenarios for each topic. However, it does not mention when not to use it or alternative tools, though the context is clear.

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