Skip to main content
Glama
VesselAPI MCP Server

VesselAPI MCP Server

search_port_events_by_port

Search port events by port name to monitor recent activity; results cover the last two hours unless a custom start time is provided.

Instructions

Search port events by port name. Covers only the last 2 hours unless timeFrom is given.

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": {
      "portName": "<portName>"
    },
    "name": "search_port_events_by_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, 1 to 50. Defaults to 20.
timeToNoEnd of the time window, RFC3339. Defaults to now.
portNameYesPort name to search for
timeFromNoStart of the time window, RFC3339. Without it the service returns only the last 2 hours.
nextTokenNoPagination token from previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per page"New value: +"Results per page, 1 to 50. Defaults to 20."
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / timeFrom
      Added value: +{
      +  "description": "Start of the time window, RFC3339. Without it the service returns only the last 2 hours.",
      +  "type": "string"
      +}
    • addedInput schema / properties / timeTo
      Added value: +{
      +  "description": "End of the time window, RFC3339. Defaults to now.",
      +  "type": "string"
      +}
  3. Addedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It usefully discloses the default 2-hour window and how timeFrom overrides it — the single most important behavior here — but says nothing about result ordering, pagination behavior, or what a 'port event' contains.

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 sentences, zero waste, and the high-impact default-window caveat is stated up front rather than buried. Nothing redundant or padded.

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?

A search tool with no annotations and no output schema should say more about what comes back and how to page. The description covers the time-window trap well but leaves the return shape and pagination semantics undocumented anywhere.

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 all five parameters including timeFrom's 2-hour default are already documented in the schema. The description repeats the timeFrom constraint without adding format, constraint, or interaction detail beyond it. 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?

States a specific verb and resource plus the scoping key: 'Search port events by port name'. That implicitly separates it from search_port_events_by_vessel and the unfiltered list_port_events, though it never names those siblings explicitly.

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?

No sentence says when to pick this over list_port_events, get_port_events, or search_port_events_by_vessel. The 'by port name' scoping implies the choice, but the agent must infer the routing from sibling names alone.

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