Skip to main content
Glama

Niche of One Network

Publish a draft to the Underground

publish_draft

Members. Publish one of your OneWriter drafts as a post on your Underground wall (or in a room you can post in), as yourself. It goes through the site's own posting rules and safety filter and is seen by members on the Underground; no public web page is made and nothing is emailed. Posts run up to 1,000 characters, so a longer draft is refused (OneWriter can download it as Markdown or HTML). At most 10 a day. Shows a preview of the exact text first; call again with confirm true and the preview_token it returned to post.

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>"
    },
    "name": "publish_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe draft to publish (from onewriter_drafts).
roomNoPost in this room instead of the main wall.
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

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the important behavior: the post goes through the site's posting rules and safety filter, is visible to members only, creates no public web page, and sends no email. It also states hard limits (1,000 characters, 10 per day) and the exact refusal behavior for over-length drafts, plus the preview/confirm/token gate that makes the write step deliberate rather than fire-and-forget.

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?

Dense but front-loaded: the action and destination come first, then visibility, then limits, then the call protocol. Almost every clause carries information the agent needs. The leading 'Members.' fragment is an odd, unexplained opener that slightly muddies the first read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write tool with no output schema, the description covers everything an agent needs to call it correctly: audience and visibility, content constraints, rate limit, failure mode, and the exact two-call sequence. Nothing material is left for the agent to discover by trial.

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 the baseline is 3, but the description adds real meaning: it explains the coupling between confirm and preview_token as a two-step preview protocol rather than two independent flags, and clarifies that room is a 'room you can post in' versus the default wall. That workflow relationship isn't obvious from the schema alone.

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 gives a specific verb and resource: publish one of your OneWriter drafts as a post on your Underground wall, optionally in a room. It also scopes authorship ('as yourself') and distinguishes draft-based publishing from a general post by naming the draft source (onewriter_drafts). It stops short of explicitly routing against the sibling post_to_underground, so the agent must infer which one applies.

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?

Usage is well framed: use it to turn an existing draft into an Underground post, with the constraint that the draft must be under 1,000 characters and a limit of 10 per day. The two-step preview-then-confirm flow is spelled out as the required call sequence. What's missing is explicit when-not guidance, e.g. naming the alternative for publishing content that isn't a 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