Skip to main content
Glama

pirate_ship_guide

Explains how to navigate Pirate Ship screens and find the sign-in link so you can start shipments, compare rates, and prepare labels. Use it first.

Instructions

How to work in Pirate Ship (shipments, rates and labels): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Pirate Ship, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. The noun 'guide' plus 'sign-in link' implies a non-mutating informational response, but the description never states that it is read-only, what form the answer takes (instructions vs. URL), or whether the returned sign-in link requires authentication to use.

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

Conciseness5/5

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

Two short sentences, zero padding, and the actionable directive ('Call this first') is included alongside the scope. Nothing could be removed without losing information.

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 single-optional-parameter, no-output-schema orientation tool, the definition covers what the guide contains and when to invoke it. The main residual gap is the expected return shape (narrative guidance vs. a link), which matters slightly more since there is no output schema.

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?

There is exactly one optional parameter, whose schema description ('What you want done in Pirate Ship, in your words') is fully covered at 100%. The description adds nothing about how to phrase the task or whether a free-form task influences what guide content is returned, so the schema does all the work.

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 identifies the resource as an orientation guide covering screens, shipments, rates, labels, and the sign-in link. It is not a crisp verb+resource statement ('How to work in...'), but the content scope is concrete enough that an agent can tell this is a documentation/entry-point tool rather than one of the action siblings like pirate_ship_click or pirate_ship_open.

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?

'Call this first' is explicit sequencing guidance that tells the agent this precedes the other Pirate Ship tools. It does not name a when-not condition or point to a specific alternative for later steps, but for an entry-point guide the primary usage rule is stated outright.

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