Skip to main content
Glama

read.wallet.points

Read-onlyIdempotent

Retrieve the Arcadia points balance for any wallet address on the Arcadia Finance platform.

Instructions

Get Arcadia points balance for a specific wallet address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_addressYesWallet address to get points for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'read.wallet.points'. It calls api.getPoints(wallet_address) to fetch the points balance for a given wallet address and returns the result as JSON.
    async ({ wallet_address }) => {
      try {
        const result = await api.getPoints(wallet_address);
        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.wallet.points' tool on the MCP server, with input schema (wallet_address string) and output schema (PointsWalletOutput).
    server.registerTool(
      "read.wallet.points",
      {
        annotations: {
          title: "Get Wallet Points",
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
        description: "Get Arcadia points balance for a specific wallet address.",
        inputSchema: {
          wallet_address: z.string().describe("Wallet address to get points for"),
        },
        outputSchema: PointsWalletOutput,
      },
      async ({ wallet_address }) => {
        try {
          const result = await api.getPoints(wallet_address);
          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,
          };
        }
      },
    );
  • PointsWalletOutput schema definition: a passthrough object (z.object({}).passthrough()) allowing any JSON shape from the API.
    export const PointsWalletOutput = z.object({}).passthrough();
  • API client method getPoints(wallet) that calls GET /points?wallet_address=... to the Arcadia API backend.
    async getPoints(wallet: string) {
      return this.get("/points", { wallet_address: wallet });
    }
  • Top-level registration: registerAllTools calls registerWalletTools(server, chains, api) which registers all wallet read tools including 'read.wallet.points'.
    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);
      registerPointsTools(server, api);
      registerGuideTools(server);
      registerWalletTools(server, chains, api);
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds no behavioral traits beyond the resource specifics, so minimal added value.

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?

Single sentence, front-loaded with verb and resource, no wasted words.

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 read tool with one required parameter and an output schema (assumed to document return values), the description is complete and sufficient.

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% for the single parameter. Description does not add any meaning beyond what the schema property description already provides.

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?

Clearly states action 'Get' and resource 'Arcadia points balance for a specific wallet address'. Distinguishes from sibling 'read.point_leaderboard' which likely returns leaderboard data.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'read.point_leaderboard'. Description only states what it does, not context or exclusions.

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