Skip to main content
Glama

List charter bases

Base_list
Read-onlyIdempotent

Sedna yacht-search guidance and available bases.

This tool lists available bases grouped by country and provides operating guidance for yacht searches.

  1. Yacht, fleet, availability and price facts come from Sedna tool results; do not invent them.

  2. Stay neutral between fleets and present factual differences so the customer can decide.

  3. Copy id_tbf1 and id_boat exactly from search_boats results.

  4. If no year is specified, clarify the date or use the current year.

  5. Call Base_list before search_boats and use the returned base name.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by saying facts must come from Sedna results, the agent should stay neutral between fleets, and IDs must be copied exactly from search_boats results. It does not describe return shape, but the annotations carry much of the burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first two sentences, but the numbered guidance includes general yacht-search rules that are not specific to listing bases, such as copying id_tbf1 and id_boat or staying neutral between fleets. These items may be useful workflow context, but they make the tool description longer and less focused than necessary.

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 zero-parameter, read-only list tool, the description is largely complete: it says bases are grouped by country, that it provides operating guidance, and that the returned base name should be used before search_boats. It does not detail the exact return fields, but the absence of an output schema makes that only a minor gap for this simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool has zero parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description does not need to compensate for any schema gaps.

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 clearly states a specific verb and resource: it 'lists available bases grouped by country' and provides operating guidance for yacht searches. It also relates itself to search_boats by instructing the agent to call Base_list first, but it does not fully distinguish itself from guidance-oriented siblings such as readme.

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?

The description gives explicit sequencing guidance: 'Call Base_list before search_boats and use the returned base name.' It also clarifies the year/date expectation when no year is specified. It does not state when not to use this tool or describe other alternatives beyond search_boats.

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