Skip to main content
Glama

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

search_journal

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_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 by structured data. The description adds only the content domain and says nothing about search semantics — whether query is full-text or substring, what happens when query is omitted, or how many results come back (the schema caps limit at 30 but the description never mentions result behavior).

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?

A single compact sentence with the subject front-loaded and no redundant wording. It is efficient, though its brevity comes at the cost of the operational detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter, read-only, closed-world search tool there is no output schema to lean on, so the description should at minimum explain what the query filters on and how many items are returned. Instead it only describes the content collection, leaving the calling semantics underspecified.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must compensate and does not: neither 'query' (max 80 chars) nor 'limit' (1–30) is mentioned or explained. The agent learns nothing about whether query matches titles, body text, or tags, or what the default result count is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the corpus ('Статьи журнала МАРШРУТА') and the content categories (guides, tips for travelers, guests and hosts), so an agent can tell it is about journal/magazine articles. However, it never states the operation itself — no 'search', 'find', or 'list' verb — so the retrieval behavior is only inferred from the tool name, and there is no explicit differentiation from siblings like search_stays or search_companions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says when to pick this over search_stays, search_companions, or get_place, and no exclusions or prerequisites are given. The only implicit cue is the content domain (editorial articles vs. listings), which the agent must derive on its own.

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