Skip to main content
Glama

Just List

Check an Event

get_event
Read-onlyIdempotent

For one of the user's Events: who claimed what and what is still unclaimed. Pass the guest link, or nothing for the most recent Event. Answers "what's still unclaimed on my event?".

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_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNoThe Event's guest link (…/p/<code>); omit for the most recent Event

Output Schema

NameRequiredDescriptionDefault
dateNo
itemsNo
titleNo
statusYes
messageYes
guestUrlNo
unclaimedNo
claimCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 closed-world, so the safety profile is handled. The description adds that it summarizes claimed vs unclaimed state, which is the conceptual payoff of the call, but it says nothing about how much data is returned or whether results are paginated or grouped per guest.

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?

It is short, front-loaded with the returned data, and the most important scoping constraint (link or nothing) comes early. The closing quoted question partly restates the opening claim, so it is slightly redundant, but nothing is bloated.

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 one-optional-parameter read tool with a cover-all annotation set and an output schema, the definition supplies everything needed to invoke it correctly. The only real omission is telling the agent how it differs from the equally named view_event sibling.

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 the single 'event' parameter is already documented in the schema. Because it is explicitly optional, the description's statement that you can pass the guest link or nothing mostly duplicates what the schema already says, so it clears the baseline but adds no new semantics.

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?

A specific verb and resource: 'For one of the user's Events: who claimed what and what is still unclaimed' tells the agent exactly what data comes back and that results are scoped to a single event. It's clear, but it never distinguishes itself from the sibling 'view_event', so an agent can't tell which one to pick from this text alone.

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 quoted user question 'what's still unclaimed on my event?' gives an implied usage trigger, and it says to omit the parameter to get the most recent Event. There is no explicit when-to-use versus when-not, and no routing to view_event or claim_item, leaving the agent to infer alternatives.

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.

Resources