Skip to main content
Glama

sitekick_site_existing_list

Read-onlyIdempotent

List currently owned existing websites as opaque choices. Use the selected page and choice token; native IDs are never input.

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>"
    },
    "name": "sitekick_site_existing_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: results are opaque choice objects rather than native IDs, which shapes how the agent must handle and feed downstream values.

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 short sentences, with the core operation stated first and the input convention second, so it is front-loaded and free of padding. Minor redundancy in "currently owned existing" costs a little precision.

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 explained, and the tool is a simple paginated read. Still missing is anything about page size, total pages relative to the schema's 0-49 bound, or how the opaque choice token returned here is consumed by sibling tools.

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 parameter burden. "The selected page" hints that the single nested `page` argument is a pagination index, but the sentence also references a "choice token" that does not appear anywhere in the input schema, which muddies rather than clarifies the argument set.

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 gives a specific verb and resource ("List currently owned existing websites") and adds the key qualifier that results are "opaque choices." It does not differentiate itself from the sibling sitekick_site_list, which also appears to enumerate sites, so an agent cannot tell from the text alone which of the two to call.

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?

"Use the selected page and choice token; native IDs are never input" gives an input convention, but it is phrased as a constraint rather than a when-to-use rule. There is no statement of when this should be preferred over sitekick_site_list or how it pairs with sitekick_site_existing_select, leaving the selection decision implicit.

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