Skip to main content
Glama
alex1092

Up Banking MCP Server

up_get_transaction

Retrieve detailed transaction information including amount, description, category, and account details using a transaction ID.

Instructions

Get detailed information about a specific transaction by ID, including amount, description, category, and related account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionIdYesThe unique identifier for the transaction

Implementation Reference

  • src/index.ts:304-318 (registration)
    Tool registration in TOOLS array, defining name, description, and input schema (transactionId required) for 'up_get_transaction'
    {
      name: "up_get_transaction",
      description:
        "Get detailed information about a specific transaction by ID, including amount, description, category, and related account.",
      inputSchema: {
        type: "object",
        properties: {
          transactionId: {
            type: "string",
            description: "The unique identifier for the transaction",
          },
        },
        required: ["transactionId"],
      },
    },
  • Handler implementation in the CallToolRequestSchema switch statement: extracts transactionId from arguments, calls client.getTransaction, and returns JSON stringified result
    case "up_get_transaction": {
      const args = request.params.arguments as { transactionId: string };
      const result = await client.getTransaction(args.transactionId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • UpApiClient.getTransaction helper method: makes API request to fetch specific transaction by ID using makeRequest
    async getTransaction(
      transactionId: string
    ): Promise<{ data: TransactionResource }> {
      return this.makeRequest(`/transactions/${transactionId}`);
    }
  • TypeScript interface defining the structure of a TransactionResource returned by the Up API
    interface TransactionResource {
      type: "transactions";
      id: string;
      attributes: {
        status: "HELD" | "SETTLED";
        rawText: string | null;
        description: string;
        message: string | null;
        isCategorizable: boolean;
        amount: MoneyObject;
        foreignAmount: MoneyObject | null;
        settledAt: string | null;
        createdAt: string;
        transactionType: string | null;
      };
      relationships: {
        account: {
          data: {
            type: "accounts";
            id: string;
          };
        };
        category: {
          data: {
            type: "categories";
            id: string;
          } | null;
        };
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error conditions, or response format details. While it implies safe retrieval, critical behavioral traits like permissions or data sensitivity are omitted, making it insufficient for a tool with zero annotation coverage.

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 that front-loads the core purpose and includes relevant details (fields retrieved). There is no wasted language or redundancy, making it appropriately sized for a simple retrieval tool with one parameter.

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 (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and fields returned, but lacks behavioral context (e.g., authentication, errors) and doesn't leverage sibling tools for better guidance. Without annotations or output schema, more completeness on usage and behavior would be beneficial.

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%, with the single parameter 'transactionId' fully documented in the schema as 'The unique identifier for the transaction'. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is added.

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 verb ('Get') and resource ('transaction'), specifying it retrieves detailed information including specific fields (amount, description, category, related account). It distinguishes from siblings like up_list_transactions by focusing on a single transaction rather than listing multiple. However, it doesn't explicitly contrast with up_get_account or up_get_category, which follow similar patterns for different resources.

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

Usage Guidelines3/5

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

The description implies usage when detailed information about a specific transaction is needed, but doesn't explicitly state when to use this versus alternatives like up_list_transactions for browsing or up_get_account for account details. No guidance on prerequisites (e.g., needing a valid transaction ID) or exclusions is provided, leaving usage context somewhat inferred rather than clearly defined.

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