Skip to main content
Glama
alex1092

Up Banking MCP Server

up_get_account

Retrieve account details including current balance and information by providing the account ID through the Up Banking MCP Server integration.

Instructions

Get details for a specific account by ID, including current balance and account information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe unique identifier for the account

Implementation Reference

  • Tool handler case that parses arguments, calls UpApiClient.getAccount, and returns the JSON-formatted result.
    case "up_get_account": {
      const args = request.params.arguments as { accountId: string };
      const result = await client.getAccount(args.accountId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Core implementation that makes the API request to retrieve the specific account details from Up API.
    async getAccount(accountId: string): Promise<{ data: AccountResource }> {
      return this.makeRequest(`/accounts/${accountId}`);
    }
  • src/index.ts:247-261 (registration)
    Registers the tool in the TOOLS array with name, description, and input schema.
    {
      name: "up_get_account",
      description:
        "Get details for a specific account by ID, including current balance and account information.",
      inputSchema: {
        type: "object",
        properties: {
          accountId: {
            type: "string",
            description: "The unique identifier for the account",
          },
        },
        required: ["accountId"],
      },
    },
  • Defines the input schema requiring accountId string.
    inputSchema: {
      type: "object",
      properties: {
        accountId: {
          type: "string",
          description: "The unique identifier for the account",
        },
      },
      required: ["accountId"],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves account details, implying a read-only operation, but doesn't address key aspects like authentication requirements, rate limits, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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?

The description is a single, efficient sentence: 'Get details for a specific account by ID, including current balance and account information.' It is front-loaded with the core purpose and includes relevant details without unnecessary words. Every part of the sentence contributes value, making it appropriately concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one required parameter, no nested objects) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it fails to explain behavioral traits or return values. The description covers the basic purpose but doesn't compensate for the lack of structured data, leaving the agent with incomplete context for safe and effective use.

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 input schema has 100% description coverage, with the 'accountId' parameter clearly documented as 'The unique identifier for the account.' The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. According to the rules, with high schema coverage (>80%), the baseline score is 3, as the schema does the heavy lifting.

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 description clearly states the tool's purpose: 'Get details for a specific account by ID, including current balance and account information.' It specifies the verb ('Get'), resource ('account'), and scope ('by ID'), making it easy to understand. However, it doesn't explicitly differentiate from siblings like 'up_list_accounts' (which likely lists multiple accounts) or 'up_get_transaction' (which retrieves transaction details), so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'up_list_accounts' for listing all accounts or 'up_get_transaction' for transaction details, nor does it specify prerequisites or exclusions. The agent must infer usage from the name and description alone, which is insufficient for optimal tool selection.

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/alex1092/up-bank-mcp-server'

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