Skip to main content
Glama
Sign In

SHIP

by ai.letsship
OverviewDiscussionsAdmin

List site waitlist

list_site_waitlist
Read-onlyIdempotent

List the addresses that the waitlist block of a site took, newest first: the address, the page of the form and the time. Only a site that SHIP made with Start from scratch has a waitlist, and the list is empty until a page with the block is published. When more addresses exist, pass nextCursor back as cursor. The addresses are personal data: the call needs the site-waitlist:read scope and an owner or an admin of the workspace, and you use the addresses only for what the user asks.

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

Input Schema

NameRequiredDescriptionDefault
limitNoAddresses per page, 1-50 (default 50)
cursorNonextCursor from the previous page; omit for the first page
siteIdYesSite id from list_sites

Output Schema

NameRequiredDescriptionDefault
dataYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the required site-waitlist:read scope, the owner-or-admin workspace permission, the personal-data handling obligation, and the conditions under which results are empty. These are exactly the behavioral facts an agent needs before calling.

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?

Well front-loaded with the resource and return shape first, then eligibility, pagination, and privacy constraints. It is a dense single paragraph and slightly long, but essentially every sentence carries actionable information.

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

Completeness5/5

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

Covers purpose, preconditions, pagination, authorization, and data-handling policy; return values are additionally backed by an output schema. Nothing an agent needs to invoke this correctly appears to be missing.

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%, so limit, cursor, and siteId are already documented, and the description largely restates the cursor round-trip. It adds little about siteId origin or limit trade-offs beyond what the schema provides, so the baseline 3 applies.

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 ('List the addresses that the waitlist block of a site took') plus the exact returned fields (address, form page, time) and ordering (newest first). This is clearly separable from siblings like remove_site_waitlist_entry or list_sites.

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 concrete eligibility conditions (only a SHIP site built with Start from scratch has a waitlist; empty until a page with the block is published) and pagination instructions (pass nextCursor back as cursor). It does not explicitly name or exclude an alternative sibling tool, which keeps it just below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SHIP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources