Skip to main content
Glama

preview_page

Read-onlyIdempotent

Verify-only composed HTML check; home preview may include requiredDecision — ask mirror vs editable before structure_*.

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": {
      "site": "<site>"
    },
    "name": "preview_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
siteYesSite slug, e.g. acme-studio
variantNoA/B variant arm to compose (e.g. "b") — same as ?dotsy-variant= on the public URL.
containsNoAssert substrings present in composed HTML.
selectorNoReturn matched elements only (tag/attrs/text).
guestTokenNoGuest token from start_site (pgg_…). Omit when signed in with OAuth.
notContainsNoAssert absent — e.g. `<dotsy-` for unresolved template tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Why you're calling this (activity log).",
      -  "minLength": 1,
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • changedInput schema / properties / guestToken / description
      Previous value: -"Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy."New value: +"Guest token from start_site (pgg_…). Omit when signed in with OAuth."
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "context"
      -]New value: +[
      +  "site"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / notContains / description
      Previous value: -"Assert absent — e.g. `<dotsy-`, `<paige-` for unresolved template tags."New value: +"Assert absent — e.g. `<dotsy-` for unresolved template tags."
  5. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this is read-only, idempotent, non-destructive, and closed-world, so the safety profile is clear. The description adds some behavioral context about a possible requiredDecision state and a mirror-vs-editable choice, but it does not explain authentication, output format, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but the dense jargon and terse em-dash clause reduce clarity. Conciseness is good, while structure and readability are only adequate.

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

Completeness2/5

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

With seven parameters, no output schema, and a verify-only operation, the description is too sparse to fully explain the tool. It omits how to interpret contains/notContains assertions, selector behavior, guestToken authentication, and what a preview result includes.

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 86%, so the schema already documents most parameters such as variant, contains, selector, guestToken, and notContains. The description adds no parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose3/5

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

The description calls this a "Verify-only composed HTML check," which gives a general action but does not clearly say it previews a page or how it differs from the sibling verify_page. The jargon "requiredDecision" and "structure_*" makes the exact purpose harder to infer.

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

Usage Guidelines2/5

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

There is a conditional instruction to ask about mirror vs editable before structure_* when a home preview includes requiredDecision, but no general guidance on when to use this tool versus verify_page, edit_page, or other preview-related siblings. Most usage selection is left to inference.

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