Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Get label settings

get_label_settings
Read-onlyIdempotent

Reads the account's label settings—size, file format, packing list, logo, USPS QR codes, address correction, and report export format—before updating them.

Instructions

Read the account's label settings from Settings, General.

Returns the size and file format new labels are made in, whether a packing list prints with them, the logo on the label, USPS label-free QR codes, what happens when Pirate Ship finds a better address, and the spreadsheet format of report exports. Read it before update_label_settings, which changes them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety bar is low. The description earns credit by enumerating the concrete settings returned — label size/format, packing list printing, logo, USPS QR codes, address correction behavior, and report export format — which is the key behavioral fact since no output schema exists. It does not mention permissions or the shape/ordering of the response object, keeping it below a 5.

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 sentences, front-loaded with the action and location of the resource, followed by useful detail. The long enumeration earns its space because it substitutes for a missing output schema.

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?

For a zero-argument read tool with no output schema and full annotation coverage, the description supplies everything an agent needs: what is read, where it lives, what comes back, and how it relates to the tool that writes the same settings.

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?

Zero parameters, so per the baseline this scores 4. The description correctly adds no parameter discussion, which is appropriate given there is nothing to call with.

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?

States a specific verb+resource and pins down the scope: reads the account's label settings from Settings, General. It also distinguishes itself from the mutating sibling update_label_settings, so the agent knows this is the read counterpart rather than a duplicate.

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?

Explicitly instructs the agent to call this before update_label_settings, naming the alternative and its relationship — a real routing rule rather than implied usage. It stops short of when-not scenarios (e.g., when cached values suffice), so it is clear context rather than full exclusion guidance.

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