Skip to main content
Glama

Niche of One Network

Send a highlight to a draft

send_highlight_to_draft

Members. Append one of your OneReader highlights or notes (by id) to a OneWriter draft, or start a new draft with it. Shows a preview first; call again with confirm true to save.

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": {
      "highlight": "<highlight>"
    },
    "name": "send_highlight_to_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoDraft id to append to.
confirmNoLeave out to preview. true writes it.
highlightYesHighlight or note id from reader_notes.
new_titleNoOr start a new draft with this title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare write/non-destructive/non-idempotent; the description usefully adds the two-phase preview-then-confirm behavior, which explains why the tool is not idempotent. It omits what the preview contains and what happens if both draft and new_title are supplied, but the safety-relevant behavior is disclosed.

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?

Two tightly written sentences with the preview/confirm rule front and center; nothing is padded. The leading fragment 'Members.' is slightly cryptic but apparently conveys an access restriction in minimal space.

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?

For a 4-parameter mutation with no output schema, the description covers the action, the two modes, and the confirm gate. Minor gaps remain (preview contents, error/mutual-exclusion behavior), but an agent has enough to call it correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: highlight ids come from OneReader, and draft vs. new_title are presented as alternative modes (append to existing vs. start new). That clarifies the relationship between two optional parameters beyond their individual schema text.

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: append a OneReader highlight/note (by id) to a OneWriter draft, or create a new draft from it. The dual mode is spelled out clearly. It does not explicitly contrast with siblings like save_to_onewriter or onewriter_drafts, which keeps it at 4 rather than 5.

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?

Gives concrete workflow guidance: the first call previews, and a second call with confirm=true commits. This tells the agent how to sequence calls. It does not name alternatives or state when a different tool (e.g., publishing or listing drafts) should be preferred.

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