Golden Flame Cologne Events

search

Search Golden Flame events, event series and guides about going out in Cologne, e.g. "Halloween party Köln ab 18", "Maskenball Köln", "Party am Rhein", "Party Hauptbahnhof Köln". Suche in Events, Reihen und Köln-Guides.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the search corpus (events, series, guides) and gives example queries, implying a read-only keyword search, but it does not disclose result format, ranking, pagination, or any limitations.

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?

Front-loads the purpose and is reasonably sized. The German translation sentence duplicates the English scope, which is redundant for most agents, but the examples earn their place by illustrating typical queries.

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

Completeness3/5

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

For a simple one-parameter search tool, the description covers purpose and query examples. However, it omits how results are returned and does not help an agent choose between search, list_events, get_event, or ask, leaving clear gaps.

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 0%, so the description must compensate. It adds example query strings that illustrate expected free-text input, but it does not explain matching fields, search behavior, or other query semantics beyond the schema's basic string type.

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?

States a specific verb (Search) and resources (Golden Flame events, event series, guides about going out in Cologne). It clearly defines scope but does not differentiate from siblings like list_events, get_event, or ask.

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?

Provides example queries but no explicit when-to-use guidance, no when-not conditions, and no alternatives among the sibling tools. An agent is left to infer that this is for keyword lookup rather than browsing or asking a question.

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

All Golden Flame Cologne Events tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?