Skip to main content
Glama
Sign In

Gangwaze

by com.gangwaze
OverviewDiscussionsAdmin

Ship profile

getShipProfile
Read-onlyIdempotent

One ship: year built and refurbished, size, guests and crew, cabin counts, rating and attribute scores, family suitability, CDC inspection score, venues and editorial. For whether a ship has a venue and which deck it is on, use getDeckPlan; for where it is right now, getShipPosition; for its cruise director, getCruiseDirector.

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": {
      "ship": "<ship>"
    },
    "name": "getShipProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
shipYesShip name, e.g. "Carnival Breeze"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope, so the safety profile is covered. The description adds useful behavioral scope by listing the profile fields returned, including editorial content and CDC inspection data, though it does not discuss permissions or response formatting.

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?

The description is two sentences: the first front-loads the tool purpose and data scope, and the second routes the agent to the right alternatives. Every sentence earns its place with no redundant restatement of the name or title.

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?

For a read-only, single-parameter profile tool with no output schema, the description is complete: it enumerates the returned data categories and points to sibling tools for related questions. The annotations cover safety behavior, and no critical invocation detail is missing.

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?

The schema has 100% description coverage and already documents the single 'ship' parameter with an example, so the schema does the heavy lifting. The description adds no additional syntax or naming guidance beyond what the schema provides.

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 'One ship:' and then enumerates the exact profile data returned, making the verb+resource purpose unmistakable. It also explicitly distinguishes this tool from getDeckPlan, getShipPosition, and getCruiseDirector, so an agent can select it without opening 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 Guidelines5/5

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

It names three alternative sibling tools and gives the precise condition for each: venue/deck questions go to getDeckPlan, current location goes to getShipPosition, and cruise director goes to getCruiseDirector. This is explicit when-to-use and when-not-to-use guidance.

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

All Gangwaze 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