Skip to main content
Glama
Sign In

Atwork

by so.atwork
OverviewDiscussionsAdmin

Create Page

page.create

Save a draft as a real page in the workspace. markdown is the body — the server converts to BlockNote. Use AFTER drafting the prose in the conversation, when the user signals 'save it' / 'make this a page' / 'add it to ' — never speculatively. The page becomes live immediately; the user has 30 seconds to undo from the trace bubble. For a named destination pass its spaceId (find a space by name with workspace.structure); omit spaceId to save in the space the user is on.

Input Schema

NameRequiredDescriptionDefault
nameYes
spaceIdNoTarget space. Omit to use the space the user is on.
folderIdNo
markdownYesStandard CommonMark. Use # for the page top-level heading (NOT the page name — the name field is separate), ## for sections, * for bullets, **bold**, *italic*. Do NOT include front matter, HTML tags, or BlockNote-specific syntax.

Output Schema

NameRequiredDescriptionDefault
nameYesPage name as stored
pageIdYesId of the created page
spaceIdYesSpace the page landed in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / spaceId / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / spaceId / type
      Added value: +[
+  "number",
+  "null"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / spaceId / description
      Added value: +"Target space. Omit to use the space the user is on."
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "markdown",
-  "spaceId"
-]New value: +[
+  "name",
+  "markdown"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the key behavioral facts: the page goes live immediately and the user has a 30-second undo window from the trace bubble. Annotations already cover readOnly/destructive/idempotent flags, and the description reinforces non-idempotency by describing promotion of a draft. It does not mention permissions or what happens if the spaceId is invalid.

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?

The core action is front-loaded and most sentences carry unique information (trigger conditions, undo window, destination resolution). The spaceId sentence partially duplicates the schema's own description, so it is slightly less efficient than it could be.

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 creation tool with an output schema, return values need not be explained; the description instead covers the crucial timing, side effects, undo window, and destination resolution. The one remaining hole is folderId and the 'name' parameter, which are undocumented in both schema and description.

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 50%, and the description mainly restates what the schema already says about spaceId ('omit to save in the space the user is on') while adding only the markdown-to-BlockNote conversion detail. The required 'name' parameter and 'folderId' are never explained, leaving a real gap for the agent.

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?

The opening sentence gives a specific verb and resource ('Save a draft as a real page in the workspace') and implicitly distinguishes this from page.update/page.edit, which modify existing pages rather than promoting a draft. It also states the markdown-to-BlockNote conversion, so the agent knows what is being produced.

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

Usage Guidelines5/5

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

Explicit when-to-use triggers are given ('when the user signals "save it" / "make this a page" / "add it to <space>"') along with a hard exclusion ('never speculatively'). It also names the sibling workspace.structure as the way to resolve a space by name.

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

All Atwork toolsInspect
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