Skip to main content
Glama

pirate_ship_read

Read the current Pirate Ship page to capture visible text and numbered buttons, links, and fields, optionally limited to one element for targeted inspection.

Instructions

Read the current Pirate Ship page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the shape of the return (text, numbered buttons, links, fields), which is useful, but it omits key behavior: whether the numbering is the identifier other tools accept, what happens when no page is open, and whether output is truncated on large pages.

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?

One sentence, front-loaded with the verb and resource, then the return contents. Nothing is wasted and there is no filler.

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?

There is no output schema, so the description must explain return values, and it does so only at a high level. For a page-inspection tool whose output feeds the click/type siblings, it should say more about the numbering scheme and failure states.

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 coverage is 100% and the single optional "element" parameter is documented there as "Read only inside this element." The description never mentions scoping to an element, so it adds nothing beyond the schema; 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?

The description uses a specific verb ("Read") with a specific resource ("the current Pirate Ship page") and enumerates what comes back: text, numbered buttons, links and fields. That clearly separates it from mutating siblings like pirate_ship_click or pirate_ship_type, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this versus pirate_ship_status, pirate_ship_guide, or the interaction tools. The only guidance is implied by the word "current" and the fact that the output is a page snapshot, leaving the agent to infer the read-then-act workflow.

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