Skip to main content
Glama

Store pickup + delivery

create_store_pickup
Destructive

Shortcut for the most common agent job: collect a prepaid order from a store and deliver it. Pickup contact gets the order reference in the instructions. The delivery card shows these details: reply in one short line instead of repeating them.

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": {
      "store_address": "<store_address>",
      "order_reference": "<order_reference>",
      "dropoff_address": "<dropoff_address>"
    },
    "name": "create_store_pickup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNo
size_classNoM
store_phoneNo
instructionsNo
workspace_idNo
store_addressYes
recipient_nameNo
dropoff_addressYes
order_referenceYes
recipient_phoneNo
item_descriptionNoPrepaid order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds response-handling guidance (the delivery card details, replying in one short line) and notes that the order reference is passed to the pickup contact, which is useful context beyond annotations. It still omits cost/payment implications and the consequences of the destructive, non-idempotent write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single short sentence and nothing is padded. The following two sentences, however, are cryptic ("the delivery card shows these details") and spend space on output formatting rather than on the many undocumented parameters.

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

Completeness2/5

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

For a destructive, non-idempotent tool with 11 parameters at 0% schema coverage and no output schema, the description is far too thin. It says nothing about pricing/payment, dryRun behavior, size_class implications, or workspace scoping, leaving significant gaps an agent needs before invoking it.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description must carry the burden, and it does not. Only order_reference, store_address, and dropoff_address are indirectly implied by the narrative; dryRun, size_class, workspace_id, store_phone, recipient_name, recipient_phone, item_description, and instructions are entirely unexplained.

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

Purpose3/5

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

The description frames the tool as a "shortcut" that collects a prepaid order from a store and delivers it, which conveys a composite pickup-plus-delivery action. However, it never states what is actually created (a delivery job? an order?) and never distinguishes itself from siblings like create_delivery or book_store_order, so an agent must infer the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

"Shortcut for the most common agent job" gives a weak implied context for use, but there is no explicit when-to-use, when-not-to-use, or named alternative for the case where only a pickup or only a delivery is needed. The agent is left to guess whether create_delivery plus book_store_order is the fallback.

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.