Skip to main content
Glama

Set up Siteprint for a coding agent

get_setup
Read-only

How to connect the person's own Siteprint designs to Claude Code, Cursor, Codex or another client: the web app's remote server with a key, or the Safari extension's local server.

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_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoclaude-code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe informational read. Beyond that it adds useful substance: there are two distinct connection paths (hosted remote server with an API key vs. local server via the Safari extension), which tells the agent the returned guidance is contingent on the user's setup. It stops short of saying what form the returned instructions take.

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?

A single dense sentence that front-loads 'How to connect' so the agent learns the tool's nature immediately. No filler; slightly compressed phrasing ('the web app's remote server with a key') but every clause carries information.

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?

For a one-optional-param, read-only, no-output-schema informational tool, the description covers what matters: what the guidance is for and the two setup paths. Missing only whether the response is step-by-step text versus a config snippet, which is minor given the tool's simplicity.

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 0%, so the description must carry the load. It does map the client families (Claude Code, Cursor, Codex, 'another client' = the 'other' enum value), which gives semantics to the sole optional parameter. However it never says how the parameter changes the returned instructions, nor that it defaults to claude-code.

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 states the resource clearly: setup instructions for connecting a person's own Siteprint designs to a coding client. It names the concrete variants (remote server with a key, Safari extension's local server), which is far more specific than the name 'get_setup' alone. It doesn't explicitly contrast itself with the sibling about_siteprint, but the setup-instruction purpose is unambiguous.

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?

Usage is implied — call it when someone wants to wire Siteprint designs into Claude Code, Cursor, Codex or another client. There is no explicit statement of when to prefer this over about_siteprint, nor any exclusion or prerequisite ('do this before list_example_designs'). Adequate but inference-based.

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