Skip to main content
Glama

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

search_companions

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

Input Schema

NameRequiredDescriptionDefault
limitNo
whereNoМесто, например «Байкал» или «Ольхон»

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: only 'open' trips are surfaced, people's profiles are not returned, and joining happens on the site after login — useful limits on what the data can be used for. It stops short of describing result volume or ordering.

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?

Three short sentences, front-loaded with what the tool returns, then the optional filter, then the constraint about profiles. The enumeration of trip types is slightly listy but earns its place by clarifying scope.

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 read-only, two-parameter search with no output schema, the description covers scope, the optional location filter, and the key limitation on returned data. Remaining gaps — default page size and result shape — are minor for a tool of this complexity.

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 50%: 'where' already documents the place with examples («Байкал», «Ольхон»), and the description only repeats that a place can be given. The 'limit' parameter (1–60) carries no meaning in either the schema or the description, so the text does not compensate for the coverage gap.

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 the resource specifically — open trips of «Попутчиков»: joint travel, free seats in tours and houses, rides — so an agent knows this is a search over travel-companion listings rather than places or journal entries. It does not explicitly contrast itself with the sibling search_stays or search_journal, even though 'домах' (houses) edges close to stays, so a 4 rather than a 5.

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?

Use is only implied: the notion of 'open trips' plus the optional 'Можно указать место' tells an agent to search with or without a location filter. There is no statement of when to prefer this over search_stays or search_journal, and no stated prerequisites.

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