Skip to main content
Glama

pirate_ship_status

Verify that your Cotlet.dev account, available credits, and Pirate Ship connection are ready before managing shipments or preparing labels.

Instructions

Check that your Cotlet.dev account and Pirate Ship are ready: account, credits and Pirate Ship connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. "Check" implies a non-mutating probe and it enumerates the three things verified (account, credits, connection), but it does not state whether a failure raises an error or returns a per-check status, nor what the response contains.

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?

A single front-loaded sentence with no filler; the only minor redundancy is restating the account and Pirate Ship connection twice across the two clauses. It is appropriately sized for a no-argument diagnostic.

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?

With no annotations and no output schema, the description would benefit from one line describing the shape of the result (per-check pass/fail vs. a single boolean) and whether a negative result is an error. For a simple zero-parameter check this is a modest gap rather than a blocking one.

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 the baseline is 4; the description's enumeration of the three checked dimensions adds useful framing about what the call inspects without needing any parameter documentation.

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 uses a specific verb ("Check") plus a named resource set — Cotlet.dev account, credits, and the Pirate Ship connection — so the agent knows this is a readiness/diagnostic tool rather than an action. It is implicitly distinguishable from the action-oriented siblings (open, click, type, read, close), though it does not name or contrast 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: "Check that ... are ready" suggests running this before attempting Pirate Ship operations, but there is no explicit when-to-use statement, no prerequisites, and no mention of what to do if the check fails. Adequate but leaves the agent to infer the sequencing.

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