Nodiom Cloud

Query node metadata

nodiom_query

Read-onlyIdempotent

Returns structural metadata about a location: exists, type, depth, childCount.

Input Schema

Name	Required	Description	Default
`doc_id`	Yes	Document ID. Examples: "waitlist", "content-calendar", "metrics".
`selector`	Yes	Structural selector. Examples: "## Signups", "## Active > li[0]", "## Active > li[contains=\"id=c_7f3a\"]". Prefer the contains form when writing: an index is a position, not an identity, so if another agent appends to the same section between your read and your write, li[0] now points at a different node and your write lands on the wrong one. A contains selector must match exactly one node or it errors rather than guessing.

Output Schema

Name	Required	Description
`type`	Yes
`depth`	Yes
`index`	Yes
`doc_id`	Yes	The document id.
`exists`	Yes
`selector`	Yes	The selector the call addressed.
`childCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "childCount": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "depth": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "doc_id": {
+      "description": "The document id.",
+      "type": "string"
+    },
+    "exists": {
+      "type": "boolean"
+    },
+    "index": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "selector": {
+      "description": "The selector the call addressed.",
+      "type": "string"
+    },
+    "type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "doc_id",
+    "selector",
+    "exists",
+    "type",
+    "depth",
+    "childCount",
+    "index"
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

B3.3/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 a list of returned fields, which overlaps with the output schema; it discloses nothing about selector resolution behavior, error conditions, or latency.

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 zero filler, and the field list is the highest-value content placed first. Nothing to trim.

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?

Return values are covered by the output schema and safety by annotations, so the description needn't repeat them. But with eight nodiom siblings sharing the same document namespace, the missing routing guidance (read vs tree vs query) leaves a real gap an agent must resolve by guessing.

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%, so both params (doc_id, selector) are already richly documented, including selector syntax, the contains-vs-index guidance, and the exact-one-match error rule. The description adds no parameter meaning beyond 'a location', so the baseline of 3 is appropriate.

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 (returns) and resource (structural metadata about a location) and enumerates the returned fields (exists, type, depth, childCount), which is more concrete than the title 'Check a section'. It does not, however, distinguish itself from siblings such as nodiom_read or nodiom_tree, so the agent must infer the boundary.

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 statement of when to use this tool versus nodiom_read, nodiom_tree, or nodiom_read_list, all of which operate on the same documents. The closest thing to guidance is the implicit 'check before write' framing in the annotations title, which the description never makes explicit.

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

All Nodiom Cloud tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.