Skip to main content
Glama
Sign In
Nodit MCP Server

Nodit MCP Server

Official
by noditlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Nodit Aptos Indexer Query Roots

list_nodit_aptos_indexer_api_query_root
Read-onlyIdempotent

Lists all query roots available in the Nodit Aptos Indexer GraphQL API, helping developers discover supported GraphQL queries before building requests.

Instructions

Lists all query roots available in the Nodit Aptos Indexer GraphQL API.

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_aptos_indexer_api_query_root"
  }
}

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the result is the complete set ('all') of query roots within the GraphQL API, with no mention of result shape, ordering, or whether a 'query root' is a name, a path, or a schema fragment. This is modest added value over the 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?

A single front-loaded sentence with no filler, hedging, or repetition. It conveys resource and scope immediately, which is the right structure for a simple enumeration tool.

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 zero parameters and no output schema, the description is the only source of information about what comes back, and it leaves the return shape undefined (list of strings vs. objects vs. structured root definitions). The safety and idempotency profile is carried by annotations, so no gap exists there, but the missing return-value hint is a real hole for a discovery tool.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The sentence correctly signals that the result is unfiltered and unscoped rather than parameter-driven.

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 ('Lists') and resource ('query roots') scoped to the Nodit Aptos Indexer GraphQL API, which distinguishes it from the execution-oriented sibling call_nodit_aptos_indexer_api. It stops short of naming that sibling or any other list_* alternative, so differentiation is implied by wording rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The enumeration framing makes the use case inferable (discover available query roots before issuing a call), but the description never says when to use it, whether it should precede call_nodit_aptos_indexer_api, or when get_nodit_aptos_indexer_api_spec is the better choice. No exclusions or prerequisites are stated.

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