Skip to main content
Glama

Find a vessel in Coast Guard records (PSIX)

uscg_vessel_search
Read-onlyIdempotent

Search the U.S. Coast Guard Port State Information Exchange by vessel name (partial match), call sign, official number, flag or service. Returns each vessel's PSIX ID, name, service, flag and status.

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

Input Schema

NameRequiredDescriptionDefault
flagNoFlag, e.g. UNITED STATES
nameNoVessel name or part of it
serviceNoService type, e.g. Towing Vessel
callSignNoCall sign
officialNumberNoOfficial number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that name matching is partial and what fields come back, but says nothing about result limits, pagination, or behavior when no criteria are supplied (all five parameters are optional).

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?

Two tight sentences: the first front-loads the data source and the searchable keys, the second front-loads the return payload. No filler, no restatement of the title.

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 read-only, open-world search with no output schema, the description covers source, inputs and returned fields adequately. The remaining gap is operational detail (result caps, empty-criteria behavior), which is minor but would matter for an agent issuing broad queries.

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%, so every parameter is already documented, including 'Vessel name or part of it' which covers the partial-match semantics the description restates. The description adds no format hints (e.g. call sign casing, official number format) or guidance on combining criteria, so it sits at the baseline.

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 (Search) and a specific resource (U.S. Coast Guard Port State Information Exchange), enumerates the searchable keys, and lists what is returned (PSIX ID, name, service, flag, status). It does not explicitly distinguish itself from the sibling uscg_vessel_profile, which likely retrieves details for a known vessel, so an agent must infer the search-vs-fetch split.

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: the enumerated lookup keys suggest 'use this when you have a name fragment, call sign, official number, flag or service.' There is no explicit when-to-use, when-not-to-use, or pointer to uscg_vessel_profile for follow-up detail, and no note that all parameters are optional or how multiple criteria combine.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.