Skip to main content
Glama

Get ways to book or contact

get_booking_options
Read-onlyIdempotent

How to reach or book AtlantFlow: phone (answered 24/7), the website callback/booking form, the contact page, and the request_service tool.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without help from the text. The description adds real operational context — phone is answered 24/7 — which is behavioral detail not present in structured fields. It does not say what the response looks like (structured list vs. prose, whether URLs/numbers are included), and there is no output schema to compensate.

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?

A single compact sentence that front-loads the purpose and then enumerates the channels. Every clause carries information — the 24/7 phone detail and the request_service cross-reference both earn their place.

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 lookup with no output schema, the description covers what the tool surfaces well enough to invoke it confidently. The only mild gap is that it does not indicate the shape of the returned content, though for a simple channel list that is a minor omission.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing the description needs to disambiguate. The description correctly implies a parameter-free lookup by listing fixed channels rather than offering filters.

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 specific resource — the ways to reach or book AtlantFlow — and enumerates the channels (phone, website form, contact page, request_service tool). It is distinguishable from siblings because it points at request_service as the action path rather than performing a booking itself. It stops short of an explicit verb like 'Returns the list of...', so the read nature is inferred from the content list.

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 implied by 'How to reach or book' — an agent can infer it should call this when a user asks about contacting or scheduling. It also references the request_service tool as one of the options, which gives a routing hint. However, there is no explicit when-to-use/when-not guidance or statement of how this differs from calling request_service directly.

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