Skip to main content
Glama
Sign In
Nodit MCP Server

Nodit MCP Server

Official
by noditlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Nodit API Spec

get_nodit_api_spec
Read-onlyIdempotent

Fetch the fully resolved spec details for a Nodit Blockchain Context API operationId and return them as JSON to guide correct API calls.

Instructions

Gets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string.

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": {
      "operationId": "<operationId>"
    },
    "name": "get_nodit_api_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYesThe operationId to get the resolved specification for. Must include the chain prefix in `{chain}-{methodName}` format (e.g., 'ethereum-eth_blocknumber', 'aptos-getAccount', 'ethereum-createWebhook'). Method-name-only input (e.g., 'eth_blocknumber') is rejected with guidance on the available chains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / operationId / description
      Previous value: -"The operationId to get the resolved specification for."New value: +"The operationId to get the resolved specification for. Must include the chain prefix in `{chain}-{methodName}` format (e.g., 'ethereum-eth_blocknumber', 'aptos-getAccount', 'ethereum-createWebhook'). Method-name-only input (e.g., 'eth_blocknumber') is rejected with guidance on the available chains."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the return format ('as a JSON string'), which is genuinely useful given there is no output schema, but it does not explain what 'fully resolved' means or how unknown operationIds behave beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose and followed by the return type; nothing redundant. It is arguably too terse for the amount of unstated context, but no sentence is wasted.

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?

With no output schema, the description should say more about the shape of the returned JSON and how it relates to invoking call_nodit_api. The return-type note is the minimum needed but leaves the agent guessing about downstream usage.

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% and the schema parameter description already specifies the {chain}-{methodName} format with concrete examples and the rejection behavior for method-name-only input. The description adds nothing beyond that, so the baseline of 3 applies.

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?

States a specific verb ('Gets') and resource ('fully resolved spec details') scoped to a Nodit Blockchain Context API operationId. It does not distinguish itself from the sibling get_nodit_aptos_indexer_api_spec, which appears to do the same thing for a different API family, so an agent must infer the split.

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 on when to call this versus preprocessing siblings like list_nodit_data_apis or the call_nodit_api family, and no stated prerequisite that the operationId must first be discovered. Usage is only implied by the phrase 'for a ... operationId'.

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