Skip to main content
Glama

Pagetool

Create anonymous draft site

draft_create

Mints an anonymous draft identity (a draft token) with no account and no sign-in. You usually do NOT need to call this first: create_site_from_brief and create_site_from_html mint one for you and return it. Use this only when you want the token before composing anything. You can edit or claim this draft for 7 days from creation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "draft_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional display name for the draft site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic mutability profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds the pieces annotations cannot: the result is an anonymous token requiring no account, and the draft is editable/claimable for 7 days from creation. That lifecycle window is exactly the kind of context that changes agent planning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what is produced, followed immediately by the usage caveat and then the expiry. No sentence is redundant; even the caveat earns its place by preventing an unnecessary call.

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 one-optional-param, non-destructive minting tool with no output schema, the description covers purpose, prerequisites (none), alternatives, and lifetime. It only stops short of stating the concrete shape of the response (e.g., the token field name), which would be useful since no output schema exists to document it.

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?

There is one optional parameter and schema coverage is 100%, so the schema already documents 'name' as an optional display name. The description adds no further meaning about the parameter, which is an acceptable baseline given high coverage, but it does not fully compensate for anything.

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 ('Mints an anonymous draft identity (a draft token)') with the qualifier 'no account and no sign-in'. It explicitly separates itself from create_site_from_brief and create_site_from_html, so an agent can identify it without opening the schema.

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?

Explicitly says the tool is usually NOT needed first, names the two sibling tools that mint a token implicitly, and gives the one condition that selects this tool ('when you want the token before composing anything'). This covers when-to-use, when-not-to-use, and the alternative in a single pass.

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