Skip to main content
Glama
Sign In

Scopeweb

by io.scopeweb
OverviewDiscussionsAdmin

create_draft

Idempotent

Stores a draft website in the user's Scopeweb portfolio and returns a persistent draft_id and a live preview_url. For when the user wants a page, site or landing draft for a name and none exists yet. Drafts persist across conversations. Content is screened on every version; a flagged draft is still stored, but its preview serves HTTP 451. Cannot spend money.

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": {
      "files": "<files>"
    },
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesSite files. index.html required for a browsable preview.
name_hintNoWorking name for the project
descriptionNoOne paragraph on what this is

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds genuinely non-obvious context beyond them: drafts persist across conversations, every version is content-screened, a flagged draft is still stored but its preview returns HTTP 451, and it cannot spend money. Those are exactly the side effects an agent needs before calling.

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?

Four short sentences that are front-loaded with the action and its outputs, then the usage condition, then behavioral caveats. Dense but every sentence carries information; only the 'cannot spend money' clause is nearly redundant given the closed-world annotation.

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 properly names the return values (draft_id, preview_url) and explains the screening/451 branch, so an agent knows what to expect from a call. Minor omissions are what happens on invalid files or whether the name_hint is used for the preview URL.

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%, so all three parameters are already documented in the schema, including that index.html is needed for a browsable preview. The description adds no syntax or format detail beyond implying 'for a name' maps to name_hint; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Stores'), resource ('draft website'), and even the outputs (persistent draft_id, live preview_url). It partially differentiates from siblings by scoping to 'a draft for a name and none exists yet', but never names create_project or update_draft, which are the closest alternatives in the sibling list.

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 a clear triggering condition: use when the user wants a page/site/landing draft for a name and none exists yet, which implicitly excludes update_draft (existing draft) and create_project. No sibling is named explicitly, so the agent must infer the boundary.

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

All Scopeweb 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