Skip to main content
Glama

Nodiom Cloud

by io.github.Synexiom-Labs
OverviewDiscussionsAdmin

Write (replace) section

nodiom_write
DestructiveIdempotent

Replaces the content at a selector. The heading is preserved. Changes are saved automatically.

Input Schema

NameRequiredDescriptionDefault
doc_idYesDocument ID. Examples: "waitlist", "content-calendar", "metrics".
contentNoSame as new_content — the name the open-source nodiom-mcp server uses.
selectorYesStructural 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.
new_contentNoNew Markdown content to place at this location.

Output Schema

NameRequiredDescriptionDefault
doc_idYesThe document id.
changedYesFalse if the content was already exactly this.
selectorYesThe selector the call addressed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "changed": {
+      "description": "False if the content was already exactly this.",
+      "type": "boolean"
+    },
+    "doc_id": {
+      "description": "The document id.",
+      "type": "string"
+    },
+    "selector": {
+      "description": "The selector the call addressed.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "doc_id",
+    "selector",
+    "changed"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: that the heading survives the replacement (i.e. only the body is destroyed) and that changes persist without an explicit save call. It does not mention auth requirements or the race-condition risk that the selector schema warns about.

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?

Three short sentences, front-loaded with the operation, then the preservation guarantee, then the persistence behavior. Every sentence carries information an agent needs and none is padding.

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?

With an output schema present, return values need no explanation, and the annotations carry the safety contract. The description covers what gets replaced and what is preserved, which is the key gap for a destructive write. It is only slightly thin on when this tool should be chosen over nodiom_append.

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 schema itself is unusually rich, including the li[0] vs contains= identity warning. The description adds nothing about doc_id, selector, or the content/new_content alias, so this sits at the baseline where the schema does all the work.

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?

"Replaces the content at a selector" gives a specific verb (replaces) and resource (section content at a selector), which implicitly contrasts with the append sibling. It stops short of naming nodiom_append or any sibling explicitly, so an agent must infer the boundary from the verb alone.

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 never states when to use this over nodiom_append, nodiom_create_doc, or other write paths, nor any prerequisites. An agent reading only this text gets no routing guidance between the two mutation siblings.

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

All Nodiom Cloud toolsInspect
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.

Resources