Skip to main content
Glama

Niche of One Network

Save to OneWriter

save_to_onewriter

Members. Create a OneWriter draft, or edit one of yours by id: title, folder (move), and text replaced or appended. Shows a preview first; call again with confirm true and the preview_token it returned to save.

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": "save_to_onewriter"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEdit this draft.
bodyNoDraft text.
modeNo
titleNoDraft title.
folderNoFolder; empty string for none.
confirmNoLeave out to preview. true writes it.
preview_tokenNoThe preview_token the preview returned. Needed with confirm true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false but say nothing about the two-phase write. The description discloses the preview/confirm handshake and the preview_token dependency, which is genuine behavior beyond structured fields. It also opens with "Members.", hinting at an access prerequisite, but does not explain permission failures or what the preview returns in detail.

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?

One dense sentence with the write flow front-loaded and no filler. The opening fragment "Members." is cryptic and the parentheticals are telegraphic, which slightly hurts readability but not length.

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?

For a 7-parameter mutation with no output schema, it should say more: whether id can be combined with title/body freely, what happens when neither is supplied, and what the preview contains. The preview_token contract is covered, but the create-versus-edit parameter contract is left to inference.

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 already 86%, so the schema carries most parameter meaning. The description adds useful mapping (folder means move, text is replaced or appended) and reiterates that preview_token pairs with confirm true, but adds no syntax rules beyond that.

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?

The description states a concrete verb and resource ("Create a OneWriter draft") and distinguishes the two operating modes: create versus edit-by-id. It is clearly not the same as a listing tool like onewriter_drafts, though it never names it explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit workflow guidance: a call without confirm produces a preview, and saving requires calling again with confirm true plus the returned preview_token. What's missing is when to prefer this over related siblings (e.g. onewriter_drafts or publish_draft).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources