agentPickup

Find pickup shops

find_shops

Read-only

Find agentPickup shops to order from: near a point (lat/lng), in a suburb or city (place), or selling something (query). Returns each shop's shop_url, pickup address, hours, whether it's open now, distance, and matching menu items.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_shops"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Where the user is: latitude. Send with lng.
`lng`	No	Where the user is: longitude. Send with lat.
`limit`	No
`place`	No	A suburb, street or city to match against shop addresses, e.g. "Surry Hills".
`query`	No	What the user wants, e.g. "flat white" or "croissant". Leave out to list everything.
`open_now`	No	Only shops open now (shops without listed hours stay in).
`radius_km`	No	With lat/lng: how far to look. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds real value by listing what comes back (shop_url, pickup address, hours, open-now flag, distance, matching menu items), but says nothing about default result counts, limit behavior, or what happens on an empty match.

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 sentences, front-loaded with the verb/resource and the mode list, followed by the useful return summary. No filler, and the return list earns its place since there is no output schema.

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

Completeness3/5

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

For a 7-parameter, zero-required search tool with no output schema, the description covers modes and return shape well but leaves the combination rules between lat/lng, place, and query undefined. Default limit and behavior with no arguments are also unstated, though radius and query defaults are handled in the schema.

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

Parameters4/5

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

Schema coverage is 86%, so the baseline is 3, but the description adds a genuinely non-schema insight: the three parameters act as alternative discovery modes rather than independent filters. It still does not clarify whether lat/lng and place can be combined, which is the main ambiguity in this 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?

States a specific verb and resource ('Find agentPickup shops to order from') and enumerates the three discovery modes, mapping each to its input (lat/lng, place, query). It cleanly separates discovery from the single-shop sibling get_shop, though it never names any sibling explicitly.

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?

The three modes give concrete usage contexts: geolocation search, area search, and item search. What is missing is any exclusion or preference guidance, e.g. when to use this versus get_shop for a known shop, or whether modes may be combined.

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

All agentPickup tools Inspect

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.