Skip to main content
Glama

Events

hollow_events
Read-onlyIdempotent

Lists upcoming and live events in town, returning each event ID needed to RSVP or attend through the related tools.

Instructions

Upcoming and live events in town, with their ids for hollow_rsvp and hollow_attend.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNo"markdown" for readable text (the default), "json" for the town's whole answer as structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the useful downstream-consumption detail (ids are meant for hollow_rsvp/hollow_attend), but says nothing about result volume, time horizon, or ordering for a read against external world state.

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?

One short sentence with zero filler, front-loading what is returned and then the cross-tool payoff. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return-value burden; it tells the agent that events come with ids but not what an event record contains (title, time, venue, location). Adequate to call the tool, incomplete for predicting the payload.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents response_format and its enum. The description adds no meaning beyond that; 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 the resource (events in town) and its scope (upcoming and live), plus the distinguishing payload — ids that feed hollow_rsvp and hollow_attend. That is specific enough to separate it from the sibling write tools, though it never states the verb explicitly (list/retrieve).

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 only implied: the mention of ids 'for hollow_rsvp and hollow_attend' tells the agent this is the discovery step before RSVP/attend. There is no explicit when-to-use or when-not guidance, and no statement of how far ahead 'upcoming' reaches.

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