Skip to main content
Glama
Sign In

Page Lemon

by com.pagelemon
OverviewDiscussionsAdmin

Read site

get_site
Read-onlyIdempotent

Reads a site: status and files (200 at a time); path: one file, paths: several; as_of or version: older copies; with site_token, whether it was claimed.

Input Schema

NameRequiredDescriptionDefault
pathNoOne file (live unless as_of or version)
siteYes
as_ofNoWith path(s): as live at this ISO date-time
pathsNoUp to 20 files, 512 KB in all
cursorNo
prefixNo
stagingNo
versionNoWith path(s): from this version number
downloadNotrue: 1-hour zip links (one per GB)
site_tokenNoFrom an anonymous deploy (secret)

Output Schema

NameRequiredDescriptionDefault
filesNo
contentNo
live_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / cursor / description
      Removed value: -"next_cursor from the last call"
    • changedInput schema / properties / download / description
      Previous value: -"true: 1-hour zip links to the live site (one per GB)"New value: +"true: 1-hour zip links (one per GB)"
    • changedInput schema / properties / paths / description
      Previous value: -"Up to 20 files, 512 KB in all (the rest say not_read)"New value: +"Up to 20 files, 512 KB in all"
    • removedInput schema / properties / prefix / description
      Removed value: -"Only files under this path"
  2. Changed3 schema fields changed
    • removedInput schema / properties / check
      Removed value: -{
-  "enum": [
-    "accessibility"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / download / description
      Previous value: -"true: 1-hour links to the whole live site as zips (one per GB)"New value: +"true: 1-hour zip links to the live site (one per GB)"
    • addedInput schema / properties / site_token / description
      Added value: +"From an anonymous deploy (secret)"
  3. Changed1 schema field changed
    • removedInput schema / properties / check / description
      Removed value: -"The full Accessibility check of the live pages (problems, fixes)"
  4. Changed3 schema fields changed
    • removedInput schema / properties / site / description
      Removed value: -"Site name"
    • removedInput schema / properties / site_token / description
      Removed value: -"From the first deploy (no account)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "files": {
+      "items": {
+        "properties": {
+          "path": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "live_revision": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  5. Changed6 schema fields changed
    • changedInput schema / properties / check / description
      Previous value: -"accessibility: the full Accessibility check of the live pages (problems, where, how to fix)"New value: +"The full Accessibility check of the live pages (problems, fixes)"
    • removedInput schema / properties / paths / maxItems
      Removed value: -20
    • changedInput schema / properties / site / description
      Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"
    • changedInput schema / properties / site_token / description
      Previous value: -"site_token from the first deploy (anonymous sites only)"New value: +"From the first deploy (no account)"
    • addedInput schema / properties / staging
      Added value: +{
+  "type": "boolean"
+}
    • 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
  6. Changed1 schema field changed
    • addedInput schema / properties / check
      Added value: +{
+  "description": "accessibility: the full Accessibility check of the live pages (problems, where, how to fix)",
+  "enum": [
+    "accessibility"
+  ],
+  "type": "string"
+}
  7. Changed1 schema field changed
    • addedInput schema / properties / download
      Added value: +{
+  "description": "true: 1-hour links to the whole live site as zips (one per GB)",
+  "type": "boolean"
+}
  8. Changed5 schema fields changed
    • removedInput schema / properties / before
      Removed value: -{
-  "description": "With versions: older than this version number",
-  "type": "integer"
-}
    • removedInput schema / properties / by
      Removed value: -{
-  "description": "With versions: by this person (part of name or email)",
-  "type": "string"
-}
    • removedInput schema / properties / since
      Removed value: -{
-  "description": "With versions: after this ISO date-time",
-  "type": "string"
-}
    • removedInput schema / properties / since_days
      Removed value: -{
-  "description": "With versions: the last N days",
-  "exclusiveMinimum": 0,
-  "maximum": 3650,
-  "type": "number"
-}
    • removedInput schema / properties / versions
      Removed value: -{
-  "description": "true: change history, newest first, 200 at a time",
-  "type": "boolean"
-}
  9. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context such as files being returned 200 at a time and older copies being available via as_of/version, but it does not explain pagination via cursor or other operational behavior beyond what the annotations provide.

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?

The description is a single compact sentence with front-loaded purpose and semicolon-separated clauses for the main modes. There is essentially no 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?

An output schema exists, so return values need not be explained, and annotations cover safety. Still, for a 10-parameter read tool with only 60% schema description coverage, the description leaves important operational concepts such as cursor-based pagination, prefix, and staging unclear, so it is only partially complete.

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 60%, and the description adds some meaning for path, paths, as_of, version, and site_token. However, several parameters, notably cursor, prefix, staging, and the required site parameter, receive no useful semantic explanation in either the description or schema, leaving notable gaps.

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 gives a specific verb and resource: it “reads a site” and enumerates status, files, single-file mode, multi-file mode, older copies, and claim status. This is clear enough for an agent to know what the tool does, though it does not explicitly distinguish itself from nearby siblings such as check_site or list_versions.

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 explains mode selection within the tool — path for one file, paths for several, as_of/version for older copies, site_token for claimed status. However, it gives no guidance on when to use this tool instead of alternatives like check_site or list_versions, and includes no exclusions.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources