Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Rename batch

rename_batch

Change the title of a batch or single label to update how it appears on the Ship page and in reports; only the displayed title changes.

Instructions

Change the title of a batch or single label.

Sets the title Pirate Ship shows on the Ship page and in reports; nothing else about the batch changes and calling it again with the same title changes nothing. Returns batch_id and the new title.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "batch_id": "<batch_id>",
      "title": "<title>"
    },
    "name": "rename_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe new title, up to 100 characters.
batch_idYesbatch_id from list_batches or create_batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.4
    • addedInput schema / properties / batch_id / description
      Added value: +"batch_id from list_batches or create_batch."
    • addedInput schema / properties / title / description
      Added value: +"The new title, up to 100 characters."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

The description does add real behavioral detail beyond the annotations: it scopes the change to the Pirate Ship display title, states nothing else in the batch changes, and names the return payload. However, "calling it again with the same title changes nothing" asserts idempotent behavior while the annotations declare idempotentHint=false — a direct conflict that an agent relying on retry semantics would be misled by. It also says nothing about permissions or failure on an invalid batch_id.

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?

Three short sentences, front-loaded with the action and effect, then scope, then return value. Every sentence carries information the agent needs given there is no output schema; no filler.

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 simple two-parameter mutation with full schema coverage and annotations present, the description covers effect, scope of change, idempotency behavior (albeit conflicting) and return shape. It stops short of covering error conditions or permission prerequisites.

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% (title length bounds, batch_id provenance from list_batches/create_batch), so the schema carries parameter semantics on its own. The description adds no format or constraint detail beyond naming batch_id as part of the return payload; baseline 3 applies.

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 concrete verb and resource ("Change the title of a batch or single label") and clarifies that only the displayed title is affected, which separates it from the many update_* siblings. Minor ambiguity in "or single label" — an agent may not immediately know a single label is addressed via batch_id.

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 implied by the effect described (retitling what appears on the Ship page and in reports), but there is no explicit when-to-use/when-not-to-use statement or comparison to any sibling such as update_label_settings or the batch creation/update tools. An agent can infer intent but gets no routing guidance.

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