Skip to main content
Glama

List Nodit Node APIs

list_nodit_node_apis
Read-onlyIdempotent

Lists available Nodit node API operations to help developers discover supported blockchain data endpoints and select the correct one for their queries.

Instructions

Lists available Nodit API operations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_nodit_node_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.5/5.0
Behavior2/5

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

The annotations already declare that the operation is read-only, idempotent, non-destructive, and not open-world. The description adds no further behavioral context, such as what the listing contains, how results are scoped, or whether there is pagination.

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?

The description is a single sentence with no filler, so it is structurally concise. However, that conciseness comes at the cost of the scoping detail needed to distinguish it from sibling tools.

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?

With no output schema and several similarly named list_* siblings, the description should clarify that this returns node API operation listings and what that output represents. Instead, it only states the generic action of listing Nodit API operations.

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

Parameters4/5

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

The tool has zero parameters, so there are no parameter semantics for the description to explain. The schema coverage is 100% and the description is not expected to compensate for missing parameter documentation.

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 says "Lists available Nodit API operations," which largely restates the title while dropping the crucial "node" scope. It does not explain what node APIs are or distinguish this listing from sibling listings such as list_nodit_data_apis, list_nodit_multichain_apis, or list_nodit_webhook_apis.

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?

There is no guidance on when to use this tool versus the many sibling list_* tools. An agent must infer that this is for discovering node-related operations rather than data, multichain, or webhook operations.

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