Skip to main content
Glama

Just List

Claim an item on an Event guest link

claim_item

For a guest: claim something to bring on a Just List Event, using the guest link the host sent and the guest's first name — exactly what the guest page allows. Pass the item's text as shown on the Event. If the item is not found, the reply lists what is still open.

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>",
      "item": "<item>",
      "firstName": "<firstName>"
    },
    "name": "claim_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe item to claim, as written on the Event
quantityNoHow many of it the guest brings (default 1)
firstNameYesThe guest's first name, shown to the host and other guests
guestLinkYesThe Event guest link (…/p/<code>)

Output Schema

NameRequiredDescriptionDefault
itemNo
eventNo
statusYes
messageYes
guestUrlNo
remainingNo
stillOpenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, destructive, idempotent, and open-world hints, and the description adds a genuine failure-mode disclosure ('If the item is not found, the reply lists what is still open'). It does not explain what happens on a repeat claim or when an item is already claimed by someone else, which matters given idempotentHint=false.

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?

Short and front-loaded, opening with the actor and action and closing with the error path. There is mild redundancy in restating the guest link and first name, which the required-parameter list already conveys.

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, so return-value documentation is unnecessary, and the description still usefully flags the not-found case. For a non-idempotent mutation it could say more about repeat claims, but nothing an agent needs to invoke it correctly is missing.

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 100% schema description coverage, the baseline is 3. The only added meaning is the emphasis on passing the item text 'as shown on the Event', which nudges toward exact-match behavior; quantity and firstName semantics are 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?

States a specific verb and resource ('claim something to bring on a Just List Event') plus the actor ('For a guest') and the inputs that scope it (guest link, first name). The 'exactly what the guest page allows' clause distinguishes it from the host-side siblings like add_items or create_list without needing to name them.

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?

Makes the operating context clear: this is the guest-facing path, used with the link the host sent plus the guest's first name, not a host-authenticated tool. It gives no explicit 'do not use when X, use sibling Y instead' routing, so it falls short of 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