Drop2Run

Read a site's settings

get_site

Read-only

Reads one site's settings and state — serving mode, password, forms, scheduled takedown, folder, whether it is paused — and its versions, newest first, with the one being served marked. Also says which settings the account's plan does not include.

Input Schema

Name	Required	Description	Default
`site`	Yes	Subdomain or site id, from list_sites.

Output Schema

Name	Required	Description
`url`	Yes	Its live URL.
`mode`	Yes	How it serves its files.
`name`	Yes	What it is called, or null.
`siteId`	Yes	Identifier of the site.
`status`	Yes	`active`, `paused`, or a state the platform put it in.
`apiProxy`	Yes	Its API proxy, or null where the proxy is not available.
`comments`	Yes	Who may comment on its pages: nobody, the people invited to comment (only while it is invite-only), or anybody signed in. Null when that could not be read.
`folderId`	Yes	The folder it is filed in, or null at the top level.
`versions`	Yes	Its versions, newest first.
`available`	Yes	Which settings the account's plan includes.
`expiresAt`	Yes	When it is scheduled to come down, or null.
`subdomain`	Yes	Its subdomain.
`invitedOnly`	Yes	Whether only invited people can open it, or null when that could not be read. Null does not mean public.
`expiryAction`	Yes	What the takedown does: `pause` or `delete`, or null when none is scheduled.
`formsEnabled`	Yes	Whether it accepts form submissions.
`formerSubdomains`	Yes	The subdomains it used to answer on, newest first; each redirects to it.
`passwordProtected`	Yes	Whether visitors must type a password.
`subdomainChangesLeft`	Yes	How many more times change_subdomain may move it, or null when there is no limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / properties / versions / items / properties / filesKept / description

Previous value: -"Whether its files are still stored; a version without them cannot be rolled back to."New value: +"Whether its files are still stored; a version without them cannot be rolled back to. The plan keeps the files of its last few versions that were live, the live one included, and lets go of older ones as newer ones go live — by count, not by age."

Changed2 schema fields changedOct 18, 2026

addedOutput schema / properties / apiProxy

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "perMonth": {
+          "description": "Proxied requests the plan allows a month; 0 when it has none.",
+          "type": "number"
+        },
+        "resetsAt": {
+          "description": "When the count starts again.",
+          "type": "string"
+        },
+        "routes": {
+          "description": "Proxy routes in the live version's _redirects.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "from": {
+                "type": "string"
+              },
+              "to": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "from",
+              "to"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "suspended": {
+          "description": "Whether the month is spent and calls answer 429.",
+          "type": "boolean"
+        },
+        "switchedOff": {
+          "description": "Whether Drop2Run switched this site's proxy off.",
+          "type": "boolean"
+        },
+        "upstreams": {
+          "description": "Origins its /api/* routes may call, as update_site's `upstream` sets them.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "blocked": {
+                "description": "Whether Drop2Run blocked this origin for every site.",
+                "type": "boolean"
+              },
+              "headers": {
+                "description": "Header names and each value's last four characters; never a value.",
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "last4": {
+                      "type": "string"
+                    },
+                    "name": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "name",
+                    "last4"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "methods": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "origin": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "origin",
+              "methods",
+              "headers",
+              "blocked"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "used": {
+          "description": "Proxied requests this month, every site of the account.",
+          "type": "number"
+        }
+      },
+      "required": [
+        "perMonth",
+        "used",
+        "suspended",
+        "resetsAt",
+        "switchedOff",
+        "upstreams",
+        "routes"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Its API proxy, or null where the proxy is not available."
+}

changedOutput schema / required

Previous value: -[
-  "siteId",
-  "name",
-  "mode",
-  "passwordProtected",
-  "invitedOnly",
-  "formsEnabled",
-  "comments",
-  "expiresAt",
-  "expiryAction",
-  "folderId",
-  "subdomain",
-  "url",
-  "status",
-  "available",
-  "versions",
-  "subdomainChangesLeft",
-  "formerSubdomains"
-]New value: +[
+  "siteId",
+  "name",
+  "mode",
+  "passwordProtected",
+  "invitedOnly",
+  "formsEnabled",
+  "comments",
+  "expiresAt",
+  "expiryAction",
+  "folderId",
+  "subdomain",
+  "url",
+  "status",
+  "available",
+  "versions",
+  "subdomainChangesLeft",
+  "formerSubdomains",
+  "apiProxy"
+]

First observedOct 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: versions are returned newest-first with the currently served one marked, and settings excluded by the account's plan are reported. It does not mention permissions/scope needed or any pagination limits, keeping it short of a 5.

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?

Two sentences, front-loaded with the verb and resource, with zero filler. The parenthetical field list is dense but every item conveys what comes back; slightly list-heavy phrasing keeps it from a 5.

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

Completeness5/5

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

An output schema exists, so return-value explanation is optional — yet the description still tells the agent the shape of the payload (current settings, version ordering, plan-gap flags), which is exactly what an agent needs to decide to call it. Nothing material is missing for a single-param read tool.

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 100% and the schema itself documents the single 'site' parameter as 'Subdomain or site id, from list_sites.' The description adds no further detail on accepted identifier forms, so it does not exceed the schema baseline.

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 ('Reads one site's settings and state') and then enumerates the concrete data returned — serving mode, password, forms, scheduled takedown, folder, paused — plus versions. This makes it clearly distinct from the sibling list_sites (list) and update_site (write).

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?

The singular 'one site's settings' implicitly frames this as the per-site read, and the schema points to list_sites for obtaining the identifier. But the description never explicitly says when to use this versus list_sites or update_site, and gives no prerequisites or exclusions.

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

All Drop2Run tools Inspect

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.