Skip to main content
Glama

pirate_ship_open

Open a Pirate Ship page in your signed-in Cloud Browser to review shipments, compare carrier rates, and prepare labels.

Instructions

Open a Pirate Ship page in your signed-in Cloud Browser (default https://www.pirateship.com) to work with shipments, rates and labels.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.pirateship.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful context — the browser is signed in and the default target is https://www.pirateship.com — but it does not say whether an existing tab is navigated or a new one opened, whether current page state is lost, what the tool returns, or how failures (not logged in, bad URL) surface.

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?

One front-loaded sentence with the verb first and the default value in parentheses; nothing is wasted. The parenthetical default partially duplicates the schema, which keeps it just short of ideal.

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?

For a simple one-optional-parameter navigation tool with no output schema, the description covers what the tool does and where it points. It is still missing return behavior and the fact that it establishes the page context the other pirate_ship_* tools operate on, which is the key thing an agent needs to sequence calls.

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 100% for the single optional url parameter, so the baseline is 3. The description restates the default URL but adds no format constraints, allowed schemes, or behavior for non-Pirate-Ship URLs.

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?

States a specific verb (Open) and resource (a Pirate Ship page in the signed-in Cloud Browser), plus the domain of work it enables (shipments, rates, labels). The verb naturally separates it from siblings like pirate_ship_close, pirate_ship_click, and pirate_ship_read, though it never names or contrasts them explicitly.

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 is only implied: the agent can infer this is the entry step before interacting with the page, and the mention of shipments/rates/labels hints at the workflow. There is no explicit when-to-use statement, no prerequisite chain (e.g., 'call this before pirate_ship_read or pirate_ship_click'), and no when-not-to-use guidance.

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