OpenAgenda
Search, analyze and manage events on OpenAgenda.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Search Docs: Find the OpenAgenda v3 operations relevant to a question. Returns operation signatures, parameters and examples to use from the `execute` tool.
- Execute: Run JavaScript against the OpenAgenda v3 API and return its result. A ready-to-use `oa` client (an OpenAgenda instance) is available. Every operation is `oa.<resource>.<action>({ path?, query
What data it sees
Do you need an account
No: the server works without sign-in
Search, analyze and manage events on OpenAgenda.
Server tool list (2)
Raw names from tools/list. Only developers need these.
| search_docs | Find the OpenAgenda v3 operations relevant to a question. Returns operation signatures, parameters and examples to use from the `execute` tool. |
| execute | Run JavaScript against the OpenAgenda v3 API and return its result. A ready-to-use `oa` client (an OpenAgenda instance) is available. Every operation is `oa.<resource>.<action>({ path?, query? })`, is async, and resolves to { data, error } — it does NOT throw on HTTP errors, so check `error`. Call search_docs to discover the full catalogue with each operation's params, response shape and a runnable example, e.g.: oa.agendas.events.list({ path: { agendaUid }, query: { relative: ["upcoming"] } }) List endpoints return { data: [...], pagination: { after } } — pass query.after to page; facets returns { facets: {...} } (no data array, no pagination). A `schemas` namespace (zod validators, prefixed z…) is also available to validate payloads. Write an async body and `return` the value you want back (JSON-serialised). Compose freely: fetch, filter and aggregate in one script; return only what you need. Sandbox: ONLY network to the OpenAgenda API is allowed (no filesystem, env or subprocess); execution is killed after 5000 ms and heap is capped at 256 MiB. |