Skip to main content
Glama

HelloCityOwl Prague Events

Search Prague events

search_prague_events
Read-onlyIdempotent

Search published Prague event facts, including ongoing programmes. Cite each event’s HelloCityOwl url and use originalUrl for the organiser’s programme. A date without a clock time has no confirmed start time.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results. Defaults to 10.
queryNoWords in the title, venue or category. All words must match, ignoring accents and case. Try DOX or music.
dateToNoLast Prague calendar day, inclusive, YYYY-MM-DD. Multi-day events are included if their dates overlap.
dateFromNoFirst Prague calendar day, inclusive, YYYY-MM-DD.
languageNoEvent language. Defaults to English on .com and Czech on .cz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond those annotations: results should cite each event's HelloCityOwl URL, use originalUrl for the organiser's programme, and treat dates without clock times as having no confirmed start time.

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 three tight sentences with the purpose front-loaded and no wasted wording. Citation rules and date semantics follow directly and 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 search tool with fully described optional parameters and no output schema, the description gives enough behavioral context to call it correctly: citation requirements, original URL handling, and date-confidence semantics. It could be slightly more complete about the overall result shape, but the essential guidance is present.

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 description coverage is 100%, so the input schema already documents all five parameters including limits, date bounds, query matching, and language defaults. The description adds a date interpretation caveat, but it does not explain the parameters themselves beyond what the schema provides.

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 states a specific verb and resource: 'Search published Prague event facts, including ongoing programmes.' It is clear what domain is searched, though 'event facts' is slightly broad and there are no siblings to distinguish it from.

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 'Search published Prague event facts,' but the description does not explicitly say when to use this tool versus alternatives or when not to use it. It provides operational guidance about citations and date interpretation rather than selection guidance.

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