Nodiom Cloud

Read list items

nodiom_read_list

Read-onlyIdempotent

Returns all list items under a selector as a JSON array of strings.

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
`items`	Yes	Each list item's source, marker and nested lines included.
`doc_id`	Yes	The document id.
`selector`	Yes	The selector the call addressed.

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": {
+    "doc_id": {
+      "description": "The document id.",
+      "type": "string"
+    },
+    "items": {
+      "description": "Each list item's source, marker and nested lines included.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "selector": {
+      "description": "The selector the call addressed.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "doc_id",
+    "selector",
+    "items"
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

B3.2/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, so the safety profile is covered. The description adds the return shape (JSON array of strings), which is mild added value, but says nothing about error behavior or selector-matching failure modes. A 3 is appropriate with annotations carrying the burden.

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 front-loaded sentence with no filler. It is efficient, though the brevity leaves nothing to route usage or caveats.

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 only 2 parameters, a full output schema, and complete annotations, the definition is technically callable as written. The missing piece is routing guidance against the many read-shaped siblings, which this description never addresses.

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 coverage is 100% and the selector description in the schema is unusually rich (contains-form guidance, exact-match requirement). The description's "under a selector" adds nothing beyond that, so the baseline 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?

States a specific verb and resource ("Returns all list items under a selector") plus the return shape, so the agent knows what it does. It does not, however, differentiate itself from siblings like nodiom_read or nodiom_query, which also read content.

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?

No indication of when to prefer this over nodiom_read, nodiom_query, or nodiom_tree, and no prerequisites or conditions given. The agent must infer usage from the name alone.

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

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.