SHIP

Get setup progress

get_setup_progress

Read-onlyIdempotent

Read what the workspace has set up with SHIP so far, as the console's setup checklist shows it: up to 13 milestones in three groups, taken in order (get started, make it yours, make it autonomous). activeGroup names the group to work on now, and each group carries its own count. Each milestone says whether it is reached and, when a console page takes it and the caller's role can, the page that does it. next names the first milestone not reached yet. Use it to suggest the next step to a person. If they say they will not finish setup, ask why and record it with report_setup_blocker.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`next`	Yes
`orgId`	Yes
`groups`	Yes
`guides`	Yes
`complete`	Yes
`totalCount`	Yes
`activeGroup`	Yes
`firstMission`	Yes
`reachedCount`	Yes
`activeGroupProgress`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties / groups / items / properties / milestones / items / properties / status

Added value: +{
+  "enum": [
+    "open",
+    "reached",
+    "completed",
+    "skipped"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / groups / items / properties / milestones / items / required

Previous value: -[
-  "id",
-  "title",
-  "description",
-  "reached",
-  "action",
-  "docsUrl"
-]New value: +[
+  "id",
+  "title",
+  "description",
+  "reached",
+  "status",
+  "action",
+  "docsUrl"
+]

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds real behavioral context the annotations don't: the ordered group model, the role-dependent gating of the per-milestone console page, and that `activeGroup`/`next` encode what to work on. Some of this restates the output schema's fields, which keeps it from being fully additive.

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?

Front-loaded with the core action and readable in one pass, with no filler sentences. It is dense in the middle with return-field detail that the output schema already carries, so a little of it could be trimmed without losing agent-relevant meaning.

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?

With annotations covering safety, an output schema defining the return shape, and no input parameters, the description supplies everything an agent needs: what the checklist contains, how groups and milestones are ordered, what `next` means, and which sibling to call when setup stalls.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The prose describes response semantics instead, which is a reasonable substitute but not parameter documentation.

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?

Opens with a specific verb and resource: 'Read what the workspace has set up with SHIP so far, as the console's setup checklist shows it.' It further scopes the payload (13 ordered milestones across three named groups) so an agent can immediately distinguish this read-only progress query from mutating siblings like mark_setup_step or report_setup_blocker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('Use it to suggest the next step to a person') and routes the adjacent case to a named sibling: if the person won't finish setup, ask why and record it with report_setup_blocker. That is a concrete when-to-use plus alternative-selection rule, not inference.

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

All SHIP tools Inspect

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.