Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get site setup

get_site_setup
Destructive

Fetch the exact files, npm packages, environment variables, and ordered steps to build or wire a Next.js site in a Cmssy workspace, avoiding setup reconstruction from docs.

Instructions

Everything needed to build a website or app on this cmssy workspace: the exact files to write (catch-all page, editor route, proxy, config, block registry, header/footer layout regions), the npm packages, the env vars filled in for this workspace (CMSSY_DRAFT_SECRET included - server-only), and the steps in order. Call it first whenever you build or wire a site, instead of reconstructing the setup from documentation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_site_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNoThe app framework. Only Next.js (App Router) is supported here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A3.6/5.0
Behavior3/5

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

It adds real context beyond the annotations: the payload contains a workspace-specific CMSSY_DRAFT_SECRET that is server-only, which is valuable handling guidance. However, annotations declare readOnlyHint=false and destructiveHint=true, and the description frames this purely as an information retrieval with no mention of any side effect, provisioning step, or why it might be destructive — a notable omission the agent cannot resolve elsewhere.

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?

One dense sentence that front-loads the payload contents and closes with the call-first instruction; every clause contributes. The long parenthetical list is heavy but appropriate for enumerating return contents.

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

Completeness4/5

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

With no output schema, the description correctly takes on the burden of describing what is returned and in what form (files plus ordered steps), which is what an agent needs to act on it. The only gap is the unexplained destructive annotation, which leaves the agent's safety expectations for this call unresolved.

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?

The single framework parameter has 100% schema coverage including an enum and a description, so the schema carries the semantics. The description never references the parameter, so baseline 3 applies.

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 enumerates exactly what the tool returns (catch-all page, editor route, proxy, config, block registry, layout regions, npm packages, env vars, ordered steps), which is far more specific than a restated title. It is clearly distinct from a plain config getter like get_site_config, though it never names that sibling explicitly.

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?

"Call it first whenever you build or wire a site, instead of reconstructing the setup from documentation" gives a clear trigger and an explicit alternative (the docs). It stops short of naming the sibling tools it supersedes or stating when not to call it (e.g. read-only inspection of an already-wired site).

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