Rynda Crewing

Search seafarer vacancies

search_vacancies

Read-onlyIdempotent

Search open vacancies for seafarers on Rynda Crewing. The order is the same for every employer and does not depend on paid plans. Filter by rank, vessel type and minimum monthly salary in USD. Returns up to 20 vacancies per call with pay, contract, joining date and port, vessel, employer and the url of the vacancy page, where the seafarer applies, plus the total number found; use page for more.

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

Input Schema

Name	Required	Description
`page`	No	Page of results, from 1.
`rank`	No	Rank (position) as people say it, e.g. "Chief Engineer", "Master", "2nd Officer", "AB", "Bosun", "Cook". Omit to search all ranks.
`limit`	No	Vacancies per page, 1 to 20.
`vessel_type`	No	Vessel type code. A group code (e.g. tanker) includes all its subtypes. tanker = Tankers; tanker_oil = Tankers: Crude oil; tanker_product = Tankers: Product; tanker_chemical = Tankers: Chemical; tanker_bunker = Tankers: Bunkering; gas = Gas carriers; dry = Dry cargo ships; dry_bulk = Dry cargo ships: Bulk carriers; dry_general = Dry cargo ships: General cargo and MPP; dry_heavy_lift = Dry cargo ships: Heavy-lift; dry_cement = Dry cargo ships: Cement carriers; container = Container ships; reefer = Reefers; roro = Ro-Ro and car carriers; passenger = Passenger ships and ferries; passenger_cruise = Passenger ships and ferries: Cruise; passenger_ferry = Passenger ships and ferries: Ferries and Ro-Pax; offshore = Offshore; offshore_supply = Offshore: PSV and AHTS; offshore_construction = Offshore: Construction and DSV; offshore_drilling = Offshore: Drilling and FPSO; offshore_crew_boat = Offshore: Crew boats; offshore_survey = Offshore: Survey; tug = Tugs and pushers; tug_towing = Tugs and pushers: Tugs; tug_pusher = Tugs and pushers: Pushers; dredging = Dredgers and technical fleet; fishing = Fishing vessels; research = Research vessels; icebreaker = Icebreakers; service = Service vessels.
`min_salary_usd`	No	Minimum monthly salary in USD. Vacancies without a stated salary are left out when this is set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious behavior: result ordering is identical for every employer and independent of paid plans, and applying happens off-tool via the vacancy URL. It does not mention rate limits or truncation beyond the 20-per-call cap.

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?

Front-loaded with purpose, then filters, then return shape and pagination — a logical order with almost no filler. The returns sentence is long and packs six payload fields plus the total and the page hint, which slightly hurts scannability.

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?

With no output schema, the description carries the return contract itself — payload fields, the 20-result cap, the total count, and how to page — plus the ordering guarantee. An agent has everything needed to call this correctly and interpret the response without further lookup.

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% and the enum is exhaustively documented in the schema, so the description only needs to stay consistent. It restates the three filters and the USD unit without adding syntax, format or edge-case meaning beyond the schema (the exclusion of salary-less vacancies is documented in the schema, not the description). 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 — 'Search open vacancies for seafarers on Rynda Crewing' — plus the filterable dimensions, which is far more than a restatement of the name. It does not explicitly contrast itself with the sibling get_vacancy, so the agent must infer that this is the list/search variant of the singular lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'use page for more' gives concrete iteration guidance, and naming rank, vessel type and min salary tells the agent which narrowing levers exist. It never states when to prefer get_vacancy for a single vacancy or when a search is unnecessary, so exclusions are absent.

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

All Rynda Crewing tools Inspect

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

Need Help?