Skip to main content
Glama
Sign In

SHIP

by ai.letsship
OverviewDiscussionsAdmin

List sites

list_sites
Read-onlyIdempotent

List the sites that SHIP hosts for the organization, newest first: the address, the template, the status and the live deploy of each. A suspension whose end is in the past reads as active. When more sites exist, pass nextCursor back as cursor.

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": "list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1-100 (default 50)
cursorNonextCursor from the previous page; omit for the first page

Output Schema

NameRequiredDescriptionDefault
dataYes
planYes
audienceNo`founder`: every project in scope is one SHIP provisioned, so a console speaks of changes and Publish. `developer`: at least one project is a repository of the caller's own, or there is no project.
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuinely non-obvious behavior: results are sorted newest first, and a suspension whose end date has passed is reported as active, which an agent could not infer from schema or annotations.

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 short sentences, front-loaded with scope and ordering, with no filler. The field enumeration ("address, the template, the status and the live deploy") is partly redundant given an output schema exists, which keeps it short of a 5.

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?

An output schema covers return values, and the description adds the pieces an agent still needs: ordering, derived status semantics, and pagination continuation. Remaining gaps are minor, such as whether results are scoped to the caller's org permissions or what an empty list implies.

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%, with limit bounds and cursor semantics already documented in the schema. The description only restates the cursor round-trip ("pass nextCursor back as cursor"), adding no format or edge-case detail beyond what is structured, so the baseline of 3 applies.

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 the sites that SHIP hosts"), plus the organizational scope and ordering ("newest first"). It does not name a sibling such as get_site to draw the single-vs-collection line explicitly, but the collection framing and field summary make the distinction readable.

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 context is implied rather than stated: the agent learns this is an org-wide listing and that pagination is continued by feeding "nextCursor" back as cursor. There is no explicit when-to-use-this-vs-get_site guidance, and no note on when a listing is preferable to fetching a single site.

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