Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set preview url

set_preview_url
Destructive

Stores the deployed app origin as the workspace preview URL so the Cmssy editor frames the correct address; use the exact deployed origin to avoid preview response errors.

Instructions

Point the cmssy editor at the deployed app: stores the origin of url as the workspace preview URL, the address the editor frames. Use the exact deployed origin (https://my-site.vercel.app) - a wrong host, such as an added www., leaves the editor reporting that the preview did not respond.

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": {
      "url": "<url>"
    },
    "name": "set_preview_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe deployed app's URL, e.g. https://my-site.vercel.app. Only its origin is stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, so the write/overwrite nature is declared structurally. The description adds real behavior beyond that: only the origin is persisted (path discarded) and an inexact host produces a silent-looking 'preview did not respond' failure. It stops short of saying explicitly that the existing preview URL is replaced or what permissions are needed.

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?

Two tight sentences: the effect is front-loaded, then the usage constraint with a concrete example. No filler, and the failure-mode warning earns its place.

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?

For a single-parameter setter with annotations covering the safety profile and no output schema, the description supplies everything needed: what gets stored, in what form, and what goes wrong otherwise.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds meaning by stressing that only the origin of the URL is retained and that the host must match the deployment exactly. This is genuinely useful semantics beyond the schema's own example.

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: 'stores the origin of url as the workspace preview URL,' and clarifies the effect ('the address the editor frames'). An agent can distinguish this from the set_* configuration siblings without opening the schema.

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 concrete usage conditions — use the exact deployed origin, and a wrong host (e.g. adding www.) breaks the preview — which is practical guidance for calling it correctly. It does not name an alternative or a when-not-to-use case, but the narrow scope makes that largely unnecessary.

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

Deploy Server

Other Tools