Skip to main content
Glama
Sign In
Nodeflare-mcp

Nodeflare-mcp

by Nodeflare-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_transaction

Fetch transaction details (from, to, value, input, block, gas) by providing a transaction hash and chain slug.

Instructions

Get a transaction by its hash (from, to, value, input, block, gas).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>",
      "hash": "<hash>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes0x-transaction hash
chainYesChain slug, e.g. 'eth', 'base', 'robinhood'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description fully carries the behavioral disclosure burden. However, it fails to mention read-only nature, error handling (e.g., missing hash), or any side effects, leaving critical behavioral traits undisclosed.

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, clear sentence of 14 words with no filler. It efficiently conveys the core purpose and return fields.

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 simplicity (2 required params, no output schema), the description covers the basics. However, it omits important contextual details such as expected behavior when the transaction is not found or if the chain is invalid.

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% with both parameters described in the schema. The description adds no semantic value beyond the schema, meeting the baseline for high coverage.

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?

The description clearly states the verb 'Get', the resource 'transaction', and the method 'by its hash', listing the fields returned. It distinguishes from sibling tools like get_transaction_receipt.

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 is provided on when to use this tool versus alternatives (e.g., eth_call, get_transaction_receipt). The description only states what the tool does, without contextual usage rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools