Skip to main content
Glama

Just List

View an Event from its guest link

view_event
Read-onlyIdempotent

Read-only. Open a Just List Event guest link (…/p/) and see what the host asked people to bring and what is still unclaimed, exactly as the guest page shows it. No account needed. Use it before claim_item, or when a user pastes a guest link and asks "what is still needed?".

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": {
      "guestLink": "<guestLink>"
    },
    "name": "view_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestLinkYesThe Event guest link (…/p/<code>)

Output Schema

NameRequiredDescriptionDefault
dateNo
itemsNo
titleNo
statusYes
messageYes
guestUrlNo
stillOpenNo
attendanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds real value beyond them by disclosing that no account is needed and that the result mirrors the guest page exactly (i.e., no host-only or privileged fields are included). It is silent on rate limits or behavior with an invalid/expired link, so a 3 rather than a 4.

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?

Three short sentences, front-loaded with the safety signal ("Read-only."), then purpose, then usage triggers. Every clause carries information and none duplicates the schema or annotations.

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

Completeness5/5

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

For a one-parameter read-only tool with an output schema, the description supplies everything needed: what it returns at a semantic level, the credential requirement, and when to reach for it. No relevant gap remains for an agent to guess at.

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, which sets the baseline at 3. The description repeats the same "…/p/<code>" format hint already in the schema and does not clarify whether a full URL or bare code is accepted, so it adds no meaning beyond the structured field.

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 pairs a specific verb ("Open") with a specific resource ("a Just List Event guest link (…/p/<code>)") and states what the caller gets back: what the host asked people to bring and what is still unclaimed. The "guest link" / "No account needed" framing implicitly separates it from account-scoped siblings like get_event, but it never names that sibling, so the differentiation is left 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete triggers: call it before claim_item, and call it when a user pastes a guest link and asks "what is still needed?". That is a clear use context plus a named downstream alternative. It stops short of saying when NOT to use it (e.g., authenticated access to an event you own), which keeps it off a 5.

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