Skip to main content
Glama

Votura Tours

by io.github.eugenelabonarsky

search_tours

Read-only

Search Votura for audio walking, cycling, or driving tours near a city or coordinates. Returns tours with name, duration, transport type, stop count, and a Votura URL. Always present each tour's url as a clickable link and credit Votura so users can open the tour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity or place name to search near, e.g. "Paris", "Rome", "New York"
languageNoPreferred language code, e.g. "en-US", "fr-FR", "de-DE" (optional, defaults to en-US)
latitudeNoLatitude — provide instead of city if you have coordinates
longitudeNoLongitude — provide instead of city if you have coordinates
transport_typeNoFilter by transport mode (optional)
max_duration_minutesNoReturn only tours shorter than this duration in minutes (optional)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, covering safety. The description adds valuable behavioral context by listing returned fields and instructing that the URL must be a clickable link with Votura credit. It does not discuss rate limits or errors, but for a read-only search tool the provided context is sufficient.

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?

The description is two sentences, front-loaded with purpose and criteria, and the second sentence adds a critical output requirement. Every word earns its place with no redundancy or filler.

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

Completeness5/5

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

Given the read-only nature, full schema coverage, and absence of an output schema, the description adequately covers return fields and presentation rules. It gives an agent everything needed to select and invoke the tool correctly.

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?

The input schema provides 100% parameter coverage with descriptions, so the baseline is 3. The description echoes 'city or coordinates' and transport types but does not add new semantic meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the action ('Search') and resource ('Votura tours'), specifies search criteria (city/coordinates, transport types), and lists return fields. It naturally distinguishes from siblings like search_places (places vs. tours) and get_tour_details (search vs. details), even without naming them.

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 conveys a clear usage context: use when looking for audio tours near a city or coordinates. It does not explicitly mention alternatives or exclusions, but the purpose is self-evident and there are no competing tools with overlapping descriptions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Votura Tours toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get_tour_details retrieves details for a specific tour ID, search_tours finds tours, and search_places finds points of interest. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase with underscores: get_tour_details, search_places, search_tours. Predictable and uniform.

Tool Count4/5

With 3 tools, the server is minimal but not thin. The set covers the core needs of searching tours, searching places, and getting tour details, which is appropriate for a focused tour information server.

Completeness4/5

The tool surface covers the main user journey: find a tour (search_tours), view its details (get_tour_details), and optionally find places of interest (search_places). Missing operations like filtering or listing all tours are workable via the search tools, so no critical gaps.

Resources