Skip to main content
Glama

Pagetool

Claim a draft into your account

draft_claim
Idempotent

Moves an anonymous draft onto the account of the signed-in user after they have authorized. Call this only once the user has said they want to keep the site - never before, and never as a precondition for building.

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_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_tokenNoThe draft token to claim. Falls back to the x-pagetool-draft-token header when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation profile is covered. The description adds the important non-obvious constraint that this is a consent-gated operation and must not be used as a gate for building. It stops short of covering what happens if the token is invalid, already claimed, or expired.

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?

Two short sentences, zero filler, with the effect stated first and the guardrail second. Every clause carries a rule an agent needs.

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-parameter, no-output-schema tool this covers the essentials: what changes, whose account, and the consent ordering. Only failure-mode behavior (invalid or already-claimed token) is left implicit.

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 description coverage is 100% and the draft_token property already documents the x-pagetool-draft-token header fallback. The description adds no meaning beyond that for the single parameter, so the baseline of 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 effect: moving an anonymous draft onto the signed-in user's account. The resource (draft), the actor (signed-in user), and the precondition (authorization) are all named, so it is distinguishable from draft_create or publish_site 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 Guidelines5/5

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

Explicitly gives the selecting condition (only after the user says they want to keep the site) and two explicit exclusions (never before, never as a precondition for building). That is a rare, unambiguous when/when-not statement.

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