Narrareach

Create article from note

create_article_from_note

Idempotent

Create a linked article draft from a Note: a draft id that list_drafts or get_draft reports with kind note. A list_notes item's top-level id is a schedule id, not a draft id; its draft.id works only when that draft is the Note itself rather than an article the Note promotes. Article drafts, including unscheduled create_draft results, are refused because they are already articles. Preserves the note; repeated requests open the same article without overwriting edits. Does not publish.

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": {
      "draftId": "<draftId>"
    },
    "name": "create_article_from_note"
  }
}

Input Schema

Name	Required	Description	Default
`writer`	No
`draftId`	Yes
`workspace`	No

Output Schema

Name	Required	Description	Default
`versions`	Yes
`articleId`	Yes
`articleLinks`	Yes
`connectedAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and closed-world, but the description goes further: it says the note is preserved, that repeats open the same article without overwriting edits, and that nothing is published. It does not address permissions, workspace scoping, or failure modes, which keeps it short of a 5.

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?

Front-loaded with the action, then the id rules, then the behavioral guarantees, with no filler. The sentence about draft.id only working 'when that draft is the Note itself rather than an article the Note promotes' is grammatically tangled and costs a re-read.

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?

An output schema exists, so return values need no explanation, and the definition covers the id disambiguation, idempotency, and non-publication behavior well. The remaining gap is the unexplained writer and workspace inputs, which matter because the schema documents nothing about them.

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 0%, so the description must carry the burden. It explains draftId in depth — what qualifies and what is rejected — but says nothing about the writer or workspace parameters, leaving two of three fields with no semantics anywhere in the definition.

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?

States a specific verb and resource: 'Create a linked article draft from a Note.' It immediately distinguishes itself from create_draft by declaring that article drafts are refused, so an agent can tell which producer to use without opening a schema.

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?

Strong negative guidance: list_notes top-level ids are schedule ids, draft.id only works when the draft is the Note itself, and article drafts (including unscheduled create_draft results) are refused. The positive precondition is implied rather than stated outright — the agent must infer 'use this when you hold a Note-kind draft id.'

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

All Narrareach tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?