Skip to main content
Glama
Sign In

agentPickup

by io.github.dav3trad3r
OverviewDiscussionsAdmin

Join a group order

join_group_order
Destructive

Add the user's items to a group order with its code. Returns the order id; pay it with pay_order before the group closes. The organiser collects everything, so the user gets a receipt, not a QR.

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": {
      "code": "<code>",
      "items": "<items>",
      "email": "<email>",
      "name": "<name>"
    },
    "name": "join_group_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe group's code
nameYesThe user's name, shown to staff on their items
emailYesThe user's email, for their receipt
itemsYes
shop_urlNoAn agentPickup shop's URL, as find_shops returns it. Defaults to https://agentpickup.app.

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?

Beyond the annotations it discloses the return value (order id), the mandatory next action (pay_order), and an important outcome distinction — the organiser collects, so the user receives a receipt rather than a QR code. It does not explain why destructiveHint is true (e.g., whether items can be removed or a join cannot be undone), which is the main remaining gap.

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?

Two tight sentences, front-loaded with the action and immediately followed by the consequence and next step. No filler or restated metadata.

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 5-parameter write tool with no output schema, it covers what is returned, the required follow-up call, and the fulfillment difference. It omits failure modes such as invalid or expired codes and whether duplicate joins are permitted, which matters given idempotentHint is false.

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 80% schema description coverage, the schema already explains code, name, email, items, and shop_url. The description only echoes 'with its code' and 'the user's items,' adding little semantic detail such as code sourcing or item-id provenance 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?

The description opens with a specific verb and resource — 'Add the user's items to a group order with its code' — which is clearly distinct from siblings like start_group_order and close_group_order. An agent can identify the operation and its mechanism without opening the 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?

It establishes the workflow context by naming the required follow-up ('pay it with pay_order before the group closes'), which tells the agent this is a mid-flow step, not a terminal one. It stops short of explicitly contrasting this with alternatives such as create_pickup_order for non-group ordering.

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