Skip to main content
Glama

Just List

Create an Event with a guest link

create_event

Create an Event (a dinner, a party, a class trip…) with the things people should bring, each with a quantity. Returns a guest link: guests open it in any browser, no app or account, and claim items with their first name. For "a birthday lunch with 12 guests", suggest items sized for 12.

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": {
      "title": "<title>",
      "items": "<items>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal date (YYYY-MM-DD) or local date and time (YYYY-MM-DDTHH:mm), as the host means it — no time zone
itemsYesWhat guests can bring, with how many are needed
titleYesEvent name

Output Schema

NameRequiredDescriptionDefault
dateNo
titleNo
statusYes
messageYes
guestUrlNo
itemCountNo
claimCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered; the description earns credit by explaining the open-world consequence in concrete terms — the tool mints a guest link that anyone can open in a browser with no app or account, and guests identify themselves only by first name. That is real behavioral context an agent needs before calling a link-generating write. It stops short of saying whether links expire, whether calling twice creates two events (non-idempotency), or how visibility is controlled.

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 sentences, front-loaded with the verb and resource, then the return value, then a concrete usage example. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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?

An output schema exists, yet the description still usefully previews the guest link, and all three parameters plus the nested items structure are accounted for. Remaining gaps are lifecycle details (link expiry, visibility, whether repeated calls duplicate events) rather than anything blocking a correct first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining what the items/quantity pair is for operationally and by giving a sizing heuristic ('for a birthday lunch with 12 guests, suggest items sized for 12') that the schema cannot express. The date parameter, including its no-time-zone convention, is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Create an Event') and immediately concretizes it with examples ('a dinner, a party, a class trip'), then states what the payload means ('the things people should bring, each with a quantity'). It also states the key output, a guest link, so the agent knows what it gets back, which is more than a bare create-tool name.

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 strongly implied: reach for this when the host wants guests to bring items without anyone installing an app or making an account, and the '12 guests' example shows the expected follow-through of sizing items to the headcount. There is no explicit when-not clause and no named alternative (e.g., create_list or draft_list), so routing between siblings is left to inference.

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