Skip to main content
Glama
Sign In

Page Lemon

by com.pagelemon
OverviewDiscussionsAdmin

Move sites to a workspace

move_sites
Destructive

Moves the person's personal sites and their Site Developers into a paid workspace. Without confirm: the questions, a recommendation and move_url (the plan is set up in the Dashboard). Then confirm: true (approve_url). Site Developers not invited lose access at once.

Input Schema

NameRequiredDescriptionDefault
modeNo
planNo
sitesNo
peopleNoSite Developer emails to invite
confirmNo
workspaceNoA paid workspace id; omit for a new one
confirm_tokenNo
personal_planNo

Output Schema

NameRequiredDescriptionDefault
move_urlNo
questionsNo
approve_urlNo
agent_messageNo
confirm_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / agent_message
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / approve_url
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / move_url
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / questions
      Added value: +{
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / members_read
      Removed value: -{
-  "description": "New workspace: every member reads form messages",
-  "type": "boolean"
-}
    • changedInput schema / properties / people / description
      Previous value: -"Site Collaborator emails to invite"New value: +"Site Developer emails to invite"
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null
  5. Changed1 schema field changed
    • changedInput schema / properties / people / description
      Previous value: -"Site Editor emails to invite"New value: +"Site Collaborator emails to invite"
  6. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already mark this as destructive, open-world, and non-idempotent, and the description adds important behavioral detail: the two-step confirmation flow and the immediate access loss for Site Developers who are not invited. It does not cover auth or rate-limit behavior, but it does disclose the key destructive consequence beyond the annotations.

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 description is three sentences and front-loads the core action before explaining the confirmation flow and access-loss warning. The phrasing around 'Without confirm: the questions...' is somewhat compressed, but there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 8-parameter destructive tool, it covers purpose, confirmation behavior, and the critical access-loss effect, and an output schema exists. Still, the low schema coverage and absence of alternative guidance or parameter explanations leave meaningful gaps for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 8 parameters and only 25% schema description coverage, the description must compensate but largely does not. It mentions confirm: true and implies people/sites handling, but leaves mode, plan, personal_plan, confirm_token, workspace, and site-selection semantics unexplained.

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?

The description states a specific verb and resource: it moves personal sites and their Site Developers into a paid workspace. The scope is clear enough to distinguish it from generic site operations, but it does not name related siblings like transfer_site or bring_back_sites.

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

Usage Guidelines3/5

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

It gives procedural guidance for the confirmation flow: without confirm it returns questions, a recommendation, and move_url, then confirm: true uses approve_url. However, it does not say when to choose this tool over alternatives such as transfer_site or bring_back_sites, nor does it state prerequisites.

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

All Page Lemon toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources