Skip to main content
Glama
Sign In

X3 Compliance

by io.github.x3allamerican
OverviewDiscussionsAdmin

Coast Guard compliance snapshot for a vessel

uscg_vessel_profile
Read-onlyIdempotent

For a PSIX vessel ID: particulars, current certificates (Certificate of Inspection, documentation, load line, class) with days left, recent inspections and incident investigations, deficiencies found and whether they are open, and flags for anything expiring or overdue.

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": {
      "vesselId": "<vesselId>"
    },
    "name": "uscg_vessel_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoLook at activities since YYYY-MM-DD (default 3 years)
vesselIdYesPSIX vessel ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is added context — and it delivers by describing what is actually returned, including derived values like days-left and open/overdue flags, which the agent cannot infer from annotations. It stops short of stating behavior for unknown IDs, data freshness, or result size.

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?

One front-loaded sentence opens with the required input, then lists outputs in a readable enumeration with no filler. The catalogue-style listing is dense but every item corresponds to real returned content, so little is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so with reasonable specificity across certificates, inspections, incidents, and deficiency status. Gaps remain around error behavior for invalid IDs and whether results are live or cached, but for a two-parameter read tool this is close to sufficient.

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%, so both parameters are already documented, including the 'default 3 years' semantics of since. The description's phrase 'recent inspections' loosely corroborates the time window but adds no format or scoping detail 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 names a concrete resource (a PSIX vessel's Coast Guard compliance record) and enumerates its contents: particulars, certificates with days remaining, inspections, incident investigations, deficiencies, and expiry flags. The verb is implicit (a retrieval) rather than stated, and it never names uscg_vessel_search as the lookup counterpart, so sibling differentiation is left to the 'PSIX vessel ID' prerequisite.

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: 'For a PSIX vessel ID' signals that an ID must already be known, which hints that this is a follow-up to an ID lookup rather than a search. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative despite uscg_vessel_search being the obvious one.

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

All X3 Compliance 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