ODocs.co

Create Document

create-document

Creates a new ODocs.co document from a title and optional initial content, and returns its id and shareable URL. Anyone who has the URL can read and edit the document; there is no per-person access control. Documents are temporary: a document is deleted after 7 days in which nobody, person or agent, opens or edits it. A signed-in user can save a document in the cloud from the editor, up to their account's limit; a saved document is kept until it is made temporary again. The editor offers a Markdown download. This tool only creates new documents; it does not change an existing one.

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": {
      "title": "<title>"
    },
    "name": "create-document"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Document title
`author`	No	Name shown on your edits and comments (e.g. "Claude via Greg"), with a robot mark as an agent. Invisible and text-direction characters are removed, line breaks and control characters become spaces, and it is cut to 256 characters. A name that resembles ODocs.co or Octaria (including look-alike spellings) is shown as "Agent (Anonymous)". When any of that happens the result has a `warning` field saying what changed.
`content`	No	Initial document content (default: empty)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare readOnly=false, destructive=false and openWorld=true; the description adds substantive, non-obvious behavior: no per-person access control on the URL, 7-day deletion on inactivity, saved documents persisting until made temporary again, and account limits. These are exactly the side effects an agent must know before creating a shareable artifact.

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 core action and return value, and the contiguity of retention and access facts is helpful. A couple of sentences about the editor's Markdown download and cloud-saving flow are product context rather than invocation guidance, slightly diluting focus.

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?

With no output schema, the description appropriately states what is returned (id and shareable URL) and covers the lifecycle and access model an agent needs. The only gap is that the author parameter and its warning-on-sanitization outcome are left entirely to the schema, though the description does mention the warning field indirectly.

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 100%, including a detailed description of the author sanitization rules and warning field, so the schema already carries parameter meaning. The description only restates title and optional content and never mentions the author parameter, adding nothing beyond the schema – baseline 3 applies.

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 ("Creates a new ODocs.co document"), names the required inputs, and discloses the return value (id and shareable URL). The closing sentence ("This tool only creates new documents; it does not change an existing one") explicitly distinguishes it from the mutation sibling patch-document.

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 clear conditions and an exclusion: only for new documents, not for changing an existing one. It does not name patch-document explicitly or state prerequisites, so the agent must infer which sibling to use for edits, but the guidance is nonetheless unambiguous about this tool's scope.

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

All ODocs.co 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?