Skip to main content
Glama
Sign In
Nodit MCP Server

Nodit MCP Server

Official
by noditlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Nodit Aptos Indexer API Spec

get_nodit_aptos_indexer_api_spec
Read-onlyIdempotent

Retrieves the GraphQL specification for a chosen Nodit Aptos Indexer API query root, helping developers inspect supported fields and build correct queries.

Instructions

Returns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API.

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": {
      "queryRoot": "<queryRoot>"
    },
    "name": "get_nodit_aptos_indexer_api_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryRootYesThe name of the query root to get the specification for. Use list_nodit_aptos_indexer_api_query_root to see available query roots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by clarifying that the response is a GraphQL specification scoped to one query root, indicating a metadata lookup rather than a data call. It does not describe error behavior or response shape, but for a simple read-only metadata tool that is a minor gap.

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, front-loaded sentence with zero filler, clearly stating the action and returned resource. Every word earns its place.

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

Completeness4/5

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

For a one-parameter, read-only metadata tool with full schema coverage and complete annotations, the description is nearly sufficient to invoke it correctly. It states the return type and scope, though it could be stronger by explicitly routing agents to the list tool and contrasting this with the call tool.

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 description coverage is 100%, and the queryRoot parameter is fully documented in the schema, including a pointer to list_nodit_aptos_indexer_api_query_root. The description adds no additional meaning about the parameter beyond identifying it as a specific query root, 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?

The description uses a specific verb, "Returns," and names the exact resource: the GraphQL specification for a specific query root in the Nodit Aptos Indexer API. It implicitly distinguishes itself from execution tools by describing a specification-returning operation, but it does not explicitly name or contrast sibling tools.

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 gives no explicit guidance on when to use this tool rather than call_nodit_aptos_indexer_api or list_nodit_aptos_indexer_api_query_root. The only navigation appears in the queryRoot schema field, which tells users to list roots first, but that is schema-level preparation rather than usage guidance in the description.

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