Skip to main content
Glama

OceanSphere Engines - marine equipment library

Models of one manufacturer

find_by_manufacturer
Read-onlyIdempotent

List models of one manufacturer, best-documented first, at most 8 per call and no paging (total_matches shows the size). Narrow with category or ship_area, or use search_equipment_models with a designation to reach a specific model.

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": {
      "manufacturer": "<manufacturer>"
    },
    "name": "find_by_manufacturer"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results; values above 8 are capped at 8.
categoryNoCategory name from list_categories, e.g. 'Radar & ECDIS'.
ship_areaNoShip area slug from list_ship_areas: engine_room, deck, electrical, navigation, safety, cargo, hvac.
manufacturerYesManufacturer name, e.g. 'Alfa Laval'.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Adds real behavior beyond the readOnly/idempotent/non-destructive annotations: a hard cap of 8 results per call, no paging, and total_matches as the escape hatch for result-set size. The cap partially duplicates the schema's limit description ('values above 8 are capped at 8'), which keeps it just short of a 5.

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, front-loaded with the core action and ordering, then the narrowing options, then the fallback to a sibling. Nothing is redundant or padded.

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?

A read-only, four-parameter lookup with an output schema and full schema coverage needs the result cap, the no-paging constraint, and the sibling alternative — all present. Nothing an agent needs in order to call it correctly 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?

Schema coverage is 100%, so manufacturer, category, ship_area and limit are already documented. The description adds only the framing that category and ship_area are narrowing filters, which is marginal value on top of an already self-documenting schema.

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?

States a specific verb and resource ('List models of one manufacturer') plus the ordering ('best-documented first'), which tells an agent exactly what comes back and in what order. It is immediately distinguishable from search_equipment_models, which is named as the alternative for designation-based lookup.

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?

Gives explicit selection logic: use this tool plus category/ship_area to narrow a manufacturer's catalog, or switch to search_equipment_models when the agent already has a designation and wants a specific model. The sibling routing is unambiguous.

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.

Resources