Skip to main content
Glama

pirate_ship_type

Types text into a specified numbered field on the current Pirate Ship page, using field numbers from the last read to target the correct input.

Instructions

Type text into a numbered field on the current Pirate Ship page.

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": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "pirate_ship_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely fails to. It doesn't say whether typing replaces or appends to existing field content, whether it triggers submit/keystroke events, what happens with an out-of-range element number, or what errors to expect. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single tight sentence with the action and target front-loaded and no filler. It is appropriately sized, though the brevity is part of why behavioral detail is missing rather than because everything necessary was said.

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?

With 2 fully documented parameters, no nested objects and no output schema, the structured data does most of the work, so the description is minimally sufficient. It falls short on the interaction contract (prerequisite read for field numbers, replace-vs-append, side effects) that an agent would need to call it correctly.

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%, with both 'text' and 'element' documented in-schema, so the baseline is 3. The description only reinforces that element refers to a 'numbered field'; it adds no format, range, or ordering guidance beyond what the schema already states.

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: 'Type text into a numbered field on the current Pirate Ship page.' An agent can distinguish it from the read/click siblings by the action verb and target. It stops short of 5 because it doesn't explicitly contrast with the sibling that would otherwise be confused (e.g., clicking a field vs typing into it).

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 only implied: 'on the current Pirate Ship page' suggests a page must already be open, and the schema's 'Field number from the last read' hints at a required prior read call, but the description never states prerequisites or when to prefer this over pirate_ship_click. No exclusions or alternatives are named.

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