Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Get Live 24h Venue Stories

get_active_stories
Read-onlyIdempotent

Fetches live 24-hour video and photo stories from clubs, organizers, and venues with direct Story Viewer 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_active_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name to filter stories for
localeNoPreferred language code (default: de)
eventIdNoFilter stories for a specific event ID

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, and closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: results are limited to a 24-hour live window, span multiple content types (video and photo), and include direct Story Viewer links in the response.

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?

A single sentence with zero filler, front-loading the core resource and its defining constraint (live 24-hour) before the source types and return value.

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 lookup tool with full annotation coverage and a fully documented schema, the description supplies enough to call it correctly and hints at the return shape via Story Viewer links. It stops short of noting whether the 24-hour window is UTC-based or whether empty results are common.

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%, with city, locale, and eventId all documented including the enum and default. The description adds no parameter-level detail such as filter combination behavior or what happens when no filters are supplied, so the schema carries the load.

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?

States a specific verb and resource: fetches live 24-hour video and photo stories from clubs, organizers, and venues. The 24-hour ephemeral scope clearly separates it from event-listing siblings like get_tonight_in_city or search_events, though no sibling is named explicitly.

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 'live 24-hour' framing implies the temporal context in which this tool applies, but there is no explicit statement of when to choose it over alternatives or when-not to use it (e.g., for past stories or archived content). Usage is inferable rather than instructed.

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.