Skip to main content
Glama

Helsinki Events

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Events

events
Read-onlyIdempotent

Find upcoming events in Helsinki, Finland (City of Helsinki Linked Events). Filter by keyword, free admission, and date window. Returns events with venue, coordinates and tags. Text is shown in English where available (else Finnish).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest event date YYYY-MM-DD.
fromNoEarliest event date YYYY-MM-DD (default: today).
pageNoPage number (default 1).
limitNoMax events (1-50, default 20).
queryNoFree-text keyword, e.g. "music", "exhibition", "kids".
free_onlyNoIf true, only free events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "free_only": true,
+    "from": "2024-01-15",
+    "limit": 20,
+    "query": "music",
+    "to": "2024-02-15"
+  },
+  {
+    "free_only": false,
+    "limit": 10,
+    "query": "kids"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnly, openWorld, idempotent, non-destructive hints. Description adds that events come with venue, coordinates, tags, and language fallback (English/Finnish). No contradictions.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficiently covers what, where, how, and return details.

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?

With no output schema, description adequately explains return values (venue, coordinates, tags). Covers all input filters and language behavior. Complete for a read-only, idempotent tool.

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 100%, so description doesn't need to detail each parameter. It groups filters (keyword, free admission, date window) which adds context, but no additional syntax or meaning beyond 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?

Clearly states 'Find upcoming events in Helsinki, Finland' with specific verb+resource+location. Distinguishes from sibling tools which are not event-finding tools.

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?

Mentions filters (keyword, free admission, date window) and return fields, providing clear usage context. No explicit when-not-to-use or alternatives, but not needed as siblings are unrelated.

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

All Helsinki Events toolsInspect
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