Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Get tracking email settings

get_tracking_email_settings
Read-onlyIdempotent

Inspect whether label recipients receive tracking emails, plus the delay, branding, and template used, to verify current notification settings.

Instructions

Read whether label recipients get a tracking email, when, and with which template.

enabled: new labels send a tracking email to the recipient by default. delay: when it goes out after the label is bought (delay_label as Pirate Ship shows it). branding: Pirate Ship's branding in the email. default_template_id: the template from list_email_templates used. update_tracking_email_settings changes these.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by explaining the semantics of the returned settings, including that delay is measured after label purchase and that enabled applies to new labels by default, which compensates for the absence of an output schema.

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?

The main purpose sentence is front-loaded, followed by a compact field glossary and a pointer to the mutating sibling. The glossary is dense but earns its place because no output schema exists; a few field explanations could be trimmed slightly.

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?

With no input parameters and no output schema, the description carries the burden of explaining what is returned, and it does so field by field. It is complete for a simple read, though it does not confirm whether these settings are account-wide or scoped to a specific label.

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 parameter semantics is a non-issue per the baseline of 4. The description instead documents the shape of the returned object, which is the relevant semantic content here.

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?

The description opens with a specific verb+resource: it reads tracking-email recipient settings, covering enabled state, send timing, and template. That scope is clearly distinct from siblings like get_label_settings or list_email_templates, so an agent can select it without inspecting the schema.

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?

The description explicitly routes changes to update_tracking_email_settings and names list_email_templates as the source for template IDs. It gives clear usage context but does not state when this read tool should be preferred over related reads such as get_label_settings.

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