Skip to main content
Glama
Sign In

Pirate Ship MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Open the browser

cotlet_browser_open
Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Pirate Ship it serves these actions: Get rates, Buy labels in bulk, Import orders, Track shipment, Refund labels.

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

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / app
      Added value: +{
+  "description": "Leave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.",
+  "pattern": "^[a-z0-9][a-z0-9-]{0,79}$",
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"A public http or https address, e.g. https://example.com. In an app's browser, a page of that app."New value: +"A public http or https address, e.g. https://example.com."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare safety flags; the description adds real behavioral context: the browser is the user's own signed-in Chrome, the URL reuses the site's existing tab so the user's other tabs survive, and the call returns the visible page elements and text with reusable numbers. That last point is valuable because no output schema exists. It doesn't mention tab state persistence across calls or failure modes, keeping it out of the top band.

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?

Front-loaded with the core action, then sequencing, then return behavior, in short declarative sentences with no wasted clauses. The trailing Pirate Ship action list is somewhat peripheral to calling the tool, though it does orient the agent to what the browser is for.

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?

There is no output schema, and the description covers the return shape ('the elements and text in view, with the same numbers'), plus the calling order and tab-reuse constraint. For a two-parameter, annotation-covered entry-point tool, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning about `url`: it lands in the site's already-open tab when one exists, otherwise a new tab. That placement rule is behavioral semantics the schema's generic URI text does not convey. The `app` parameter's subtlety lives entirely in the schema, not the description.

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 specific verb and resource: it starts the user's Cloud Browser (a real Chrome, signed in to their sites) and opens `url`. That is more concrete than the tool name alone and distinguishes it from click/fill/scroll siblings. It does not explicitly differentiate itself from the closely named cotlet_browser_navigate, so it falls short of a 5.

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 it first" gives explicit ordering guidance relative to the other browser tools, which is the main usage question for an entry-point tool. It does not say when NOT to use it, e.g. versus cotlet_browser_navigate for an already-open browser, so it stops short of full alternative routing.

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

All Pirate Ship MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources