Skip to main content
Glama
Sign In
rustpad-mcp

rustpad-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Append to a pad

append_to_document

Append text to the end of a collaborative pad while preserving all concurrent edits. Use a leading newline to start a new line.

Instructions

Appends text to the end of a pad, leaving everything else — including concurrent edits — untouched. The text is appended verbatim; include a leading newline to start a new line.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "text": "<text>"
    },
    "name": "append_to_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the pad, the part after # in its URL
textYesText to append verbatim

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesShareable; anyone with it can read and edit.
noteYes
charactersYesLength of the pad after the write, in codepoints.
appended_charactersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "appended_characters": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "characters": {
+      "description": "Length of the pad after the write, in codepoints.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "id": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "url": {
+      "description": "Shareable; anyone with it can read and edit.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "url",
+    "characters",
+    "note",
+    "appended_characters"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the tool as non-read-only and non-destructive, and the description adds the concurrency-safety note ('including concurrent edits') and the verbatim handling of text. It does not disclose potential errors, permissions, or return behavior, but given the annotations cover the safety profile, the added context is modest.

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?

The description is two sentences, front-loaded with the primary purpose, and contains no filler. Every phrase adds meaning: the verbatim behavior, the concurrency guarantee, and the newline tip.

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?

The tool is simple with only two parameters, both documented, and an output schema is present. The description covers the core behavior, concurrency safety, and a usage nuance. It does not mention error handling or authentication, but these are not critical for an append operation given the existing annotations and schema coverage.

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 schema provides complete descriptions for both parameters (id and text), so the baseline is 3. The description adds a practical usage tip (include a leading newline to start a new line) that goes beyond the schema's text description, providing real value for correct invocation.

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

Purpose5/5

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

The description clearly states the action ('appends text to the end of a pad') and identifies the specific resource (a pad). It explicitly contrasts with set_document and replace_in_document by noting that everything else, including concurrent edits, remains untouched, making the tool's unique purpose unambiguous.

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 description implies usage context (adding content to existing pads) and gives a concrete tip about leading newlines, but it does not explicitly name alternative tools or conditions for when to prefer this over set_document or replace_in_document. The guidance is helpful but not fully explicit on tool selection.

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