Skip to main content
Glama

search_places

Find nearby restaurants, shops, and landmarks by coordinate or named area, with category and radius filters.

Instructions

Find places — restaurants, shops, landmarks — near a point or in a named area. Costs $0.002 per call, paid in USDC over x402 to x402-places. Returns the merchant's artifact and the payment receipt.

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": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query
latNoLatitude
lonNoLongitude
kindNoPlace category filter
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.
radiusNoMetres

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does the highest-value part: it discloses a concrete cost ($0.002 per call), the payment asset and rail (USDC over x402 to x402-places), and the return payload (merchant's artifact plus payment receipt). Gaps remain on failure behavior — what happens when payment fails, empty results, or pagination — which matters for a paid call.

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, zero filler: the capability and scope come first, then cost, payment path, and return shape. Payment terms are essential for this tool and are stated compactly rather than buried.

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 six-parameter paid search tool with no annotations and no output schema, the return description and payment mechanics cover a lot, but the description never states that some location or query input is effectively needed (0 required parameters) nor what an empty or failed paid call looks like. An agent could invoke it with no arguments and no expectation of the result shape beyond 'artifact plus receipt'.

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 the schema already defines all six parameters including the rail enum, so the baseline of 3 applies. The description adds a point-vs-named-area framing, but 'named area' does not map cleanly to any parameter (q is described only as 'free-text query'), leaving a small ambiguity rather than resolving one.

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 places') and enumerates the domain ('restaurants, shops, landmarks'), which separates it from search_flights and search_hotels by subject matter. It also names the two search modes ('near a point or in a named area'). It stops short of naming a concrete sibling alternative, so it is clear but not maximally differentiated.

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?

Usage is only implied by the phrase 'near a point or in a named area' — there is no explicit when-to-use/when-not statement, no guidance on which combination of q, lat/lon, kind, and radius to supply, and no mention of the sibling tools it should be preferred over. The pricing sentence adds context but is not usage guidance.

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