Skip to main content
Glama
Sign In
Nodit MCP Server

Nodit MCP Server

Official
by noditlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Nodit Webhook APIs

list_nodit_webhook_apis
Read-onlyIdempotent

Lists available Nodit Webhook API operations so developers can identify endpoints for configuring real-time blockchain event notifications.

Instructions

Lists available Nodit Webhook 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_webhook_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.8/5.0
Behavior2/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. The description adds nothing beyond that — it does not say whether results reflect a live catalog, how many operations are returned, or how the output should feed downstream calls.

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?

A single short sentence with no filler and the key noun front-loaded. It is efficient, though its brevity is close to under-specification rather than disciplined concision.

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 no parameters, the description carries the full burden of explaining what the agent receives — yet it never describes the return shape (list of operation names? paths? identifiers?) or how to use the results. For a discovery tool that exists only to feed other calls, that omission is a real gap.

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 and the schema is a bare empty object, so there is no parameter meaning for the description to supply. Baseline 4 applies for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("Lists ... Webhook API operations"), so the basic action is unambiguous. However, "operations" is vague about what is actually returned (endpoint names, IDs, categories?), and it makes no attempt to distinguish this catalog from sibling catalogs such as list_nodit_data_apis or list_nodit_node_apis beyond the word "Webhook".

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 when-to-use guidance: nothing says to call this before invoke-style tools such as call_nodit_api or get_nodit_api_spec, and nothing states when a different catalog sibling is the right choice. The agent must infer the workflow from the tool name alone.

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