Skip to main content
Glama

Keep an anonymous site

claim-site
Idempotent

Move an anonymous site published earlier in this conversation into the signed-in user's Flowershow account, so it no longer expires and can be updated with publish using siteId alone. Use when the user wants to keep a site that was published without an account. Needs the siteId and claimToken returned by that earlier publish. If the user is not signed in yet, calling it asks them to sign in to Flowershow first.

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": {
      "siteId": "<siteId>",
      "claimToken": "<claimToken>"
    },
    "name": "claim-site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYessiteId of the anonymous site
claimTokenYesclaimToken returned when the anonymous site was created

Output Schema

NameRequiredDescriptionDefault
nameYes
siteIdYes
liveUrlYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-readOnly, so the safety profile is covered; the description adds real context beyond them: ownership transfer to the signed-in user, removal of the expiry, and the auth gate ('calling it asks them to sign in to Flowershow first'). It does not describe what happens with an expired or invalid claimToken, which is the main remaining behavioral gap.

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?

Three sentences, front-loaded with the action and effect, then the trigger, then prerequisites and auth behavior. Nothing is padding, though the second sentence's restatement of token provenance mildly duplicates the schema.

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?

A low-complexity, two-parameter tool with a full schema and an output schema, so return values need no explanation; the description covers purpose, trigger, prerequisites, and auth behavior. Only the failure mode for an invalid or expired claimToken is unaddressed.

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 coverage is 100% and both parameter descriptions already explain siteId and claimToken provenance, so the description mostly restates that the token comes from the earlier publish. It adds only a light implication that siteId persists as the handle for later publish calls; baseline 3 is appropriate.

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 ('Move an anonymous site ... into the signed-in user's Flowershow account') plus the concrete effect (no longer expires, publishable with siteId alone). This clearly separates it from the publish sibling, which creates sites rather than adopting existing ones.

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 an explicit trigger: 'Use when the user wants to keep a site that was published without an account.' It also states the precondition (siteId and claimToken from the earlier publish). It does not explicitly name publish as the alternative path or say when not to use it, but the context is narrow enough that little is left ambiguous.

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.