Skip to main content
Glama

pickup_points

Pickup points (lockers, shops) near a street address, closest first, where the printer offers 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": {
      "ship_to": "<ship_to>"
    },
    "name": "pickup_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to list (1–20, default 5).
ship_toYesDelivery address: a JSON file, inline JSON, or - for stdin. As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description contributes the ordering rule (closest first) and the qualification that only points the printer offers are returned, which are real behaviors not in the annotations. However, with annotations present but terse (readOnlyHint false, openWorldHint true), it does not clarify whether the call has side effects or hits an external service, which matters given the open-world hint.

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?

A single dense sentence with the resource, examples, ordering, and scope front-loaded, and no filler. Nothing could be removed without losing meaning.

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 values need not be explained, and both parameters are fully described in the schema. What is left implicit is which printer's point network applies and whether pricing or availability comes back, a minor gap for a two-parameter lookup tool.

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% and ship_to is documented there in detail, down to country-specific field sets, so the schema carries the parameter burden. The description only restates that lookup happens near a street address and adds no constraints or formats for limit or ship_to beyond the schema.

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

Purpose4/5

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

Names a specific resource (pickup points, with examples lockers and shops), a scope (near a street address), and an ordering (closest first), which makes its function unambiguous. It does not explicitly contrast with any sibling such as address_validate or order_create, so it stops short of full differentiation.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative. Usage is only implied: an agent infers this is the pre-order lookup for delivery points, but nothing states that relation to order_create or address_validate.

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