Skip to main content
Glama

sitekick_site_existing_select

DestructiveIdempotent

Select one currently owned existing website using its opaque choice token and original idempotency key. Registration does not adopt or publish it.

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": {
      "payload": "<payload>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_site_existing_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare a destructive, idempotent, open-world mutation, and the description adds meaningful scoping context that registration neither adopts nor publishes the site. However, it never explains what the call actually changes or consumes, so the destructiveHint remains unexplained. The 'currently owned' wording hints at a precondition but never states it.

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?

Two tight sentences, front-loaded with the action and inputs. The second sentence is valuable but slightly jarring since it introduces 'Registration' where the tool is named 'select', briefly blurring what operation is being performed.

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

Completeness3/5

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

An output schema exists, so return values need not be described. Still, for a destructive, nested-payload mutation with zero parameter documentation coverage, the description says nothing about reversibility, what happens to the site's ownership state, or why a page index is required.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden. It meaningfully characterizes two of the three leaf parameters (the opaque choice_token and the 'original' idempotency key, hinting at key reuse), but the required numeric 'page' field inside the payload is never mentioned and its purpose is not obvious for a single-site selection.

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?

States a concrete verb and resource ('Select one currently owned existing website') plus the identifying inputs, which separates it from the listing/inspection siblings. The closing clause ('does not adopt or publish it') further distinguishes it from sitekick_adoption_capture, though no sibling is named explicitly.

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 only implied: the agent must infer that the 'choice token' comes from sitekick_site_existing_list and that this call is the follow-up to it. There is no explicit when-to-use/when-not guidance and no statement of prerequisites such as ownership scope.

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