Skip to main content
Glama
Sign In

Pirate Ship MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Refund labels in Pirate Ship

pirate_ship_refund_labels
Read-onlyIdempotent

Refund labels in the user's own Pirate Ship account from ChatGPT, Claude or any AI agent. Returns how to do it in Pirate Ship step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Pirate Ship Cloud Browser. Pirate Ship's official API: Pirate Ship has no API (checked 11 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent and non-destructive, and the description adds the critical behavioral fact that it 'opens nothing by itself' — it only returns instructions, not side effects. It also discloses that Pirate Ship has no official API (with a checked date), which explains why a browser-based follow-up is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence about returning steps and not acting is front-loaded and useful, but 'from ChatGPT, Claude or any AI agent' is marketing filler that adds no selection value. The closing API note is relevant but awkwardly phrased ('Pirate Ship's official API: Pirate Ship has no API').

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?

For a zero-parameter, annotation-rich guide tool with no output schema, the description conveys enough: what it returns, that it performs no action, and which tools carry out the refund. A slightly clearer statement of the returned format would make it fully self-sufficient.

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 at 100% schema coverage, so there is nothing for the description to disambiguate. The baseline of 4 for a parameterless schema 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 states concretely that the tool returns step-by-step instructions (screens, buttons, fields) for refunding labels in Pirate Ship, which resolves the ambiguity created by the action-flavored name 'pirate_ship_refund_labels'. It distinguishes itself from the cotlet_browser_* tools it points to, but does not differentiate from the other pirate_ship_* or cotlet_app_guide siblings.

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?

It gives clear workflow context: call this to get instructions, then execute them with the cotlet_browser_* tools in the user's Pirate Ship Cloud Browser. There is no explicit when-not or guidance on when cotlet_app_guide would be the better choice, so it stops short of full routing.

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

All Pirate Ship MCP Server and API by Cotlet 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