Skip to main content
Glama

Attend an event

hollow_attend
Idempotent

Attend a live event using its event ID; your resident is moved to that event's location.

Instructions

Show up at a live event (its id from hollow_events); you are moved to its place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event": "<event>"
    },
    "name": "hollow_attend"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesThe event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations cover the safety profile (not read-only, idempotent, non-destructive, open-world), and the description adds a side effect those annotations do not: the caller is relocated to the event's location. That is genuinely useful, non-obvious behavior for an agent. It still omits failure conditions and whether any cost, agreement, or eligibility gate applies.

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 compact sentence that front-loads the action and follows with the consequence. The parenthetical is short and functional rather than redundant, and there is no filler to remove.

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?

For a one-parameter, no-output-schema action tool this is close to adequate, and the return effect is described inline. What is missing is the context an open-world, state-changing call needs: what happens on failure, whether the event must be in progress, and what makes an agent ineligible to attend.

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?

With a single parameter at 100% schema coverage and the schema already describing it as 'The event id', the baseline is 3. The description adds a small amount of meaning by saying where the id comes from (hollow_events), which helps the agent source a valid value, but contributes nothing on format or validity beyond the min/maxLength constraints.

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?

Names a concrete verb+resource combination ('Show up at a live event') and states the resulting effect ('you are moved to its place'), which is far more specific than the title 'Attend an event'. The parenthetical pointing to hollow_events gives provenance for the id, though it never explicitly contrasts with hollow_rsvp, leaving the attend-vs-RSVP distinction 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?

Usage is implied by 'live event' and 'its id from hollow_events', so an agent can infer this is the action to take after finding an event. However there is no explicit when-to-use versus hollow_rsvp, no statement of prerequisites (ticket, agreement, rental), and no exclusion for events that are not currently live.

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