Skip to main content
Glama

TransactionGet

Retrieve transaction details from RushDB's graph database by providing a transaction ID to access specific financial or data records.

Instructions

Get information about a transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionIdYesTransaction ID

Implementation Reference

  • The core handler function implementing the TransactionGet tool. It fetches the transaction by ID from the database and returns its ID with a success message.
    export async function TransactionGet(params: { transactionId: string }) {
      const { transactionId } = params
    
      const transaction = await db.tx.get(transactionId)
    
      return {
        id: transaction.id,
        message: `Transaction information retrieved successfully`
      }
    }
  • Schema definition for the TransactionGet tool, including input validation requiring a transactionId string.
    {
      name: 'TransactionGet',
      description: 'Get information about a transaction',
      inputSchema: {
        type: 'object',
        properties: { transactionId: { type: 'string', description: 'Transaction ID' } },
        required: ['transactionId']
      }
    },
  • index.ts:519-530 (registration)
    Registration and dispatch logic in the MCP server's CallToolRequest handler switch statement, which calls the TransactionGet handler.
    case 'TransactionGet':
      const transactionInfo = await TransactionGet({
        transactionId: args.transactionId as string
      })
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(transactionInfo, null, 2)
          }
        ]
      }
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. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data or raw information, or has any side effects. The description is minimal and lacks important behavioral context for a tool with no 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 extremely concise with just one sentence containing no wasted words. It's front-loaded with the core purpose and efficiently communicates the basic function without unnecessary elaboration.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned about transactions, whether this includes metadata or just status, or how the output relates to other transaction tools. The minimal description leaves significant gaps in understanding the tool's full behavior and output.

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 schema has 100% description coverage with the transactionId parameter clearly documented. The description adds no additional parameter information beyond what the schema provides. With complete schema coverage, the baseline score of 3 is appropriate since the description doesn't need to compensate for schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get information about a transaction' clearly states the verb ('Get') and resource ('transaction'), but it's vague about what specific information is retrieved. It distinguishes from siblings like TransactionBegin/Commit/Rollback by focusing on retrieval rather than transaction management, but doesn't specify what kind of transaction data is returned.

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. There's no mention of prerequisites (needing a transaction ID), comparison to similar tools like GetRecord or GetRecordsByIds, or context about when transaction information is needed versus record information.

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/rush-db/RushDB'

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