Skip to main content
Glama

vibo_list_events

Read-only

List upcoming events you host or attend, switch to past events, and filter by title to find the event you need.

Instructions

List the events you're part of (as host or guest). Defaults to upcoming events; pass past:true for events that have already happened. Optionally filter by a search query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vibo_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch events by title.
pastNoReturn past events instead of upcoming (default false).
skipNoNumber of items to skip, for paging (default 0).
viewNo"full" (default) returns Vibo's payload as it arrived; "brief" returns one line per event: title — <ISO date | no date> — <your role>, <open|locked>, inside the untrusted-data envelope, with "-- none" for no events and "-- N of M shown" / "-- more" when the page is partial.
limitNoMax items to return (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns Vibo's payload as it arrived; \"brief\" returns one line per event: title — <ISO date | no date> — <your role>, <open|locked>, inside the untrusted-data envelope, with \"-- none\" for no events and \"-- N of M shown\" / \"-- more\" when the page is partial.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a non-mutating, open-world read. The description adds the membership scoping constraint and the upcoming/past default, but says nothing about pagination behavior, result volume, or what a filtered-empty result looks like beyond what the schema's view parameter already explains.

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?

Three short sentences, front-loaded with the scope constraint, then the default behavior, then the optional filter. No filler or repetition, though the closing sentence about filtering is the weakest since the schema already describes q.

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?

With five optional parameters and no output schema, an agent gets enough to call this correctly: scope, default time window, paging switches and filter all resolve through the schema. It stops short of explaining pagination semantics or partial-page behavior, which matters for a list tool but is partially covered by the view parameter description.

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 100%, so q, past, skip, limit and view are all documented in the schema itself. The description only restates the past flag and mentions an optional search filter, adding no syntax or format detail beyond the structured fields; baseline 3 applies.

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?

The description names a specific verb and resource (list events) and constrains scope to events the caller is host or guest of, which is genuinely informative. It does not name the sibling vibo_get_event or otherwise distinguish itself from single-event retrieval, so sibling differentiation is left to inference.

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?

It gives useful default behavior (upcoming, not past) and the exact switch (past:true) for historical results, which is real guidance for parameter selection. However, it never says when to reach for this versus vibo_get_event for a specific event, and there are no stated exclusions or prerequisites.

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