Skip to main content
Glama

Search places

search_places
Read-onlyIdempotent

Answers: which place is meant when a name is ambiguous, such as several towns with the same name. The user's favorite locations whose names match come first. Optionally ranks the other results near another place or "here".

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": {
      "query": "<query>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoA place name or "here" to rank results near.
queryYesA place name, or part of one.

Output Schema

NameRequiredDescriptionDefault
linkNo
noteNo
sourceNoSource: UAV Forecast
statusYesok or subscription_required; others may appear.
messageNo
resultsNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context: favorites are ranked first, and optional proximity ranking via 'near' affects ordering. It does not explain result count or what 'here' resolves to, but the output schema covers return values.

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

Conciseness4/5

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

The description is short and front-loads the primary disambiguation purpose before describing ordering behavior. The colon-style opening is slightly awkward but not wasteful.

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 two-parameter read-only search with an output schema and complete annotations, the description supplies enough about purpose, favorites-first ranking, and optional proximity ordering. It could be slightly more explicit about returning place candidates, but no critical invocation information is missing.

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 coverage is 100%, so both parameters are already documented in detail. The description reinforces that 'near' accepts another place or 'here' and that ranking is optional, but adds little beyond the schema text.

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?

The description states a specific function: resolving ambiguous place names, prioritizing matching favorites, and optionally ranking by proximity. It does not explicitly say it returns a list of place records, but the search intent is clear and siblings are unrelated weather/settings tools.

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 implied by 'when a name is ambiguous,' which gives a reasonable trigger condition. However, there is no explicit when-not guidance or comparison to alternative tools, leaving the agent to infer that this is the initial place-resolution step.

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