Skip to main content
Glama

МАРШРУТ — Байкал и Россия

about_marshrut

Read-only

Как устроен МАРШРУТ: бронирование и оплата, отмена, клуб и бонусы, «Попутчики», хозяевам.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful topical scope but does not say whether the information is static, current, or comprehensive, nor does it clarify the return form. With annotations carrying the behavioral safety burden, a 3 is appropriate.

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?

The description is a single front-loaded sentence with no redundant wording. The enumerated topic list is efficient, though the final item 'хозяевам' is slightly telegraphic and could be more clearly framed.

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 simple, no-parameter informational tool with annotations covering read-only behavior and no output schema, the description is largely complete: it states the resource and the topics covered. A minor gap is that it does not explicitly describe the tool as an explanatory/help resource rather than a transactional one.

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 no parameters, so there is no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description does not introduce any parameter-related ambiguity.

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 identifies this as an informational overview of how the service works and enumerates the covered topics: booking/payment, cancellation, club/bonuses, travel companions, and hosts. It is clear enough to distinguish from action-oriented siblings, but it does not explicitly state that it is an overview/FAQ-style tool.

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 the topic list: an agent would call this for general questions about the service. However, there is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative such as redirecting booking actions to prepare_booking.

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