Skip to main content
Glama

Paris Events

by io.github.pipeworx-io
OverviewAdmin

Events

events
Read-onlyIdempotent

Find current "things to do" in Paris (Que Faire à Paris, City of Paris official events). Filter by keyword, free admission, and date window. Returns events sorted by start date. Note: titles/descriptions are in French.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclude events starting on/before this date YYYY-MM-DD.
fromNoInclude events running on/after this date YYYY-MM-DD (default: today). Ongoing/undated events are included.
limitNoMax events (1-50, default 20).
queryNoKeyword (full-text), e.g. "jazz", "exposition", "marché". French terms match best.
offsetNoPagination offset (default 0).
free_onlyNoIf true, only free events (price_type = gratuit).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "free_only": true,
+    "from": "2025-01-15",
+    "limit": 10,
+    "query": "jazz"
+  },
+  {
+    "from": "2025-01-01",
+    "limit": 20,
+    "query": "exposition",
+    "to": "2025-03-31"
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already confirm read-only, idempotent, non-destructive behavior. The description adds that results are sorted by start date and that titles/descriptions are in French, which provides modest additional behavioral context beyond annotations.

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 succinct sentences, front-loading the core purpose and key filters. Every sentence adds value, with no redundancy or extraneous information.

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 read-only event search with 6 optional parameters and no output schema, the description covers main filters, sorting, and language. It is mostly complete, though pagination (offset) behavior or default date windows could be mentioned.

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 the baseline is 3. The description restates filtering dimensions already present in the schema (keyword, free, date window) without adding new semantic detail beyond what the schema provides.

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 tool finds current 'things to do' in Paris from the official City of Paris events API, with specific filter options (keyword, free, date window). It distinguishes itself effectively from sibling tools, none of which target events.

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?

The description implies usage for finding Paris events but lacks explicit guidance on when to use vs alternatives. No 'when not to use' or comparison to siblings is provided, leaving the agent to infer context.

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

All Paris Events 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.

Resources