Skip to main content
Glama

Openagenda

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Events

events
Read-onlyIdempotent

List events from one OpenAgenda agenda (get its uid from search_agendas). Defaults to upcoming events. Optionally filter by keyword and date window. Returns title, dates, venue, coordinates and keywords (English where available, else French).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest event date YYYY-MM-DD.
fromNoEarliest event date YYYY-MM-DD (default: today, upcoming only).
sizeNoMax events to return (1-50, default 20).
queryNoKeyword filter over the agenda’s events.
agenda_uidYesAgenda uid from search_agendas, e.g. "6008621".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "agenda_uid": "6008621"
+  },
+  {
+    "agenda_uid": "6008621",
+    "from": "2024-01-01",
+    "query": "concert",
+    "size": 30,
+    "to": "2024-12-31"
+  }
+]
  2. First observed

TDQS

A4.4/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 open-world. Description adds that results default to upcoming events, and return specific fields with language preference (English where available, else French). This provides useful 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?

Two sentences, no wasted words. Front-loaded with purpose and essential details (source uid, defaults, optional filters, return fields). Every sentence contributes.

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?

Without an output schema, the description lists return fields (title, dates, venue, coordinates, keywords), which is adequate. Mentions language preference. Could optionally note pagination via 'size', but it's handled in schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with descriptions for all 5 parameters. Description adds value by stating default behavior: 'from' defaults to today (upcoming), 'size' defaults to 20, and 'query' is a keyword filter. These clarify schema semantics.

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?

Description clearly states it lists events from a single OpenAgenda agenda, referencing the source uid from sibling tool 'search_agendas'. It specifies defaults (upcoming events) and optional filters, and lists return fields. This distinguishes it clearly from sibling tools like search_agendas.

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?

Explicitly instructs to get the uid from search_agendas, which is a sibling tool. It implies when to use (when you have an agenda uid) and describes optional filters. Lacks explicit when-not-to-use scenarios, but the context is sufficient.

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

All Openagenda 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