Skip to main content
Glama
AdamikHQ

Adamik MCP Server

Official

getTransactionDetails

Retrieve blockchain transaction information by specifying chain ID and transaction ID to access details like status, timestamps, and involved addresses.

Instructions

Gets info about a transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainIdYes
transactionIdYes

Implementation Reference

  • The handler function that fetches transaction details from the Adamik API using makeApiRequest and returns a text content response with JSON-stringified data.
    async ({ chainId, transactionId }: GetTransactionDetailsPathParams) => {
      const transaction = await makeApiRequest<GetTransactionDetailsResponse>(
        `${ADAMIK_API_BASE_URL}/${chainId}/transaction/${transactionId}`,
        ADAMIK_API_KEY
      );
    
      const text = JSON.stringify(transaction);
      return {
        content: [
          {
            type: "text",
            text,
          },
        ],
      };
    }
  • Zod schemas and TypeScript types for the input path parameters (chainId, transactionId) and response (transaction details and status) of the getTransactionDetails tool.
    export const GetTransactionDetailsPathParamsSchema = z.object({
      chainId: ChainIdSchema,
      transactionId: z.string(),
    });
    export type GetTransactionDetailsPathParams = z.infer<typeof GetTransactionDetailsPathParamsSchema>;
    
    export const GetTransactionDetailsResponseSchema = z.object({
      transaction: TransactionDetailSchema,
      status: TransactionStatusSchema,
    });
    export type GetTransactionDetailsResponse = z.infer<typeof GetTransactionDetailsResponseSchema>;
  • src/module.ts:406-429 (registration)
    Registration of the getTransactionDetails tool using server.tool(), including name, description, input schema validation, and handler function.
    server.tool(
      "getTransactionDetails",
      "Gets info about a transaction",
      {
        chainId: ChainIdSchema,
        transactionId: z.string(),
      },
      async ({ chainId, transactionId }: GetTransactionDetailsPathParams) => {
        const transaction = await makeApiRequest<GetTransactionDetailsResponse>(
          `${ADAMIK_API_BASE_URL}/${chainId}/transaction/${transactionId}`,
          ADAMIK_API_KEY
        );
    
        const text = JSON.stringify(transaction);
        return {
          content: [
            {
              type: "text",
              text,
            },
          ],
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states only that it 'gets info', implying a read-only operation, but doesn't specify whether it's idempotent, has rate limits, requires authentication, returns structured data, or handles errors. For a tool with two required parameters and no output schema, this leaves critical behavioral traits undocumented, though it doesn't contradict any annotations.

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 at three words, with zero wasted language. It's front-loaded with the core action ('Gets info'), though this brevity comes at the cost of completeness. Every sentence (here, a single phrase) earns its place by stating the basic purpose, but it's under-specified rather than efficiently informative.

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?

Given the complexity (two required parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what information is returned, how to interpret parameters, or behavioral aspects like error handling. For a tool that likely retrieves detailed transaction data in a blockchain context, this minimal description leaves the agent with significant gaps in understanding how to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It adds no meaning beyond what the schema provides—no clarification on what 'chainId' and 'transactionId' represent (e.g., numeric chain identifiers, transaction hashes), their formats, or examples. With two required parameters and zero coverage, the description fails to provide necessary semantic context, leaving the agent to guess parameter usage.

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

Purpose2/5

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

The description 'Gets info about a transaction' is a tautology that merely restates the tool name 'getTransactionDetails'. It lacks specificity about what kind of information is retrieved (e.g., status, amount, participants, timestamps) or what domain this operates in (blockchain transactions). While it correctly identifies the verb 'gets' and resource 'transaction', it provides no meaningful differentiation from what the name already conveys.

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 offers no guidance on when to use this tool versus alternatives. With sibling tools like 'getAccountHistory' and 'getAccountState' available, there's no indication whether this tool is for transaction-level details versus account-level queries, or whether it requires specific prerequisites like chain connectivity. The agent must infer usage from the name alone, which is insufficient for informed 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/AdamikHQ/adamik-mcp-server'

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