Skip to main content
Glama
Sign In

agentPickup

by io.github.dav3trad3r
OverviewDiscussionsAdmin

Start a group order

start_group_order
Destructive

Start a group order (a coffee run) at a shop, when the user wants to order together with others now. Returns a code to share: each person's agent joins with it and pays for their own items. When it closes, the shop gets one combined order and the organiser is emailed its pickup QR. To share agentPickup itself with a friend, use share_agentpickup instead.

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": {
      "organiser_name": "<organiser_name>",
      "organiser_email": "<organiser_email>"
    },
    "name": "start_group_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoe.g. "Friday coffee run"
shop_urlNoAn agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app.
organiser_nameYesWho collects, shown to staff
organiser_emailYesWhere the group's pickup QR goes
closes_in_minutesNoDefault 15

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is covered. The description adds real context beyond that: it returns a shareable code, each participant pays for their own items, the shop receives one combined order, and the organiser is emailed the pickup QR. It never explains why the operation is flagged destructive (e.g. what closing/abandoning does), which keeps it from a 5.

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?

Three tight sentences, front-loaded with the action and the trigger, then the return value, then the sibling redirect. Every sentence carries information; only the parenthetical '(a coffee run)' is decorative.

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?

There is no output schema, and the description compensates by explaining what is returned (a share code) and the downstream lifecycle (join, individual payment, combined order, emailed QR). For a five-parameter creation tool this is enough for an agent to call it correctly.

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 every parameter is already documented in the schema, and the baseline of 3 applies. The description reinforces the role of the organiser email (where the group's pickup QR goes) but adds no format or constraint detail beyond what the schema states.

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 ('Start a group order (a coffee run) at a shop') and immediately distinguishes itself from the sibling share_agentpickup. An agent can tell this apart from create_pickup_order or join_group_order without opening any schema.

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?

Gives a clear triggering condition ('when the user wants to order together with others now') and explicitly routes the share-a-friend case to share_agentpickup. It does not contrast against create_pickup_order for solo orders, so the alternative coverage is partial rather than exhaustive.

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

All agentPickup toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources