Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get User Saved Events

get_my_saved_events
Read-onlyIdempotent

Retrieves bookmarked events and favorites when an auth token or UID is supplied, or returns direct personal bookmarks links.

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": "get_my_saved_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoPreferred language code (default: de)
userTokenOrIdNoOptional Firebase user ID token or UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new context: results depend on whether a token or UID is supplied, versus falling back to links. It stops short of explaining what that fallback actually returns.

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?

A single sentence with the primary behavior front-loaded; no filler. The 'or returns direct personal bookmarks links' clause is vague rather than wasteful, but it slightly undercuts clarity.

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 simple read-only, zero-required-parameter tool with full schema coverage and annotations, the description covers most of what an agent needs. The main gap is not clarifying what happens when no token or UID is provided.

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?

Schema coverage is 100%, so both parameters are documented in the schema. The description adds meaning by linking userTokenOrId to the behavior (authenticated bookmarks vs. fallback), though it says nothing about the locale parameter and leaves the fallback semantics ambiguous.

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 ('Retrieves bookmarked events and favorites'), which distinguishes it from generic discovery siblings like search_events. It is weakened by the trailing clause about 'direct personal bookmarks links', which muddies what the tool actually returns.

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?

Usage is implied conditionally: supply an auth token or UID to get bookmarks and favorites. There is no explicit statement of when to prefer this over siblings such as get_event_details or search_events, and no guidance on the no-parameter case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.