Skip to main content
Glama

search_places

Read-onlyIdempotent

Search Swiss place names, localities, mountains, and geographic features by query for location lookup and geodata discovery.

Instructions

Search place names, localities, mountains, geographic features

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
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • removedInput schema / properties / query / description
      Removed value: -"Place name to search"
    • removedInput schema / properties / type
      Removed value: -{
      -  "description": "Type filter: locations, featuresearch",
      -  "type": "string"
      -}
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered by structured data. The description adds nothing beyond that - no word on matching behavior (fuzzy vs prefix), result limits, language handling, or what a hit contains - so it earns no credit for behavioral disclosure.

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?

It is very short and front-loaded with no filler, which is good, but it is an unpunctuated noun-phrase fragment rather than a complete sentence, and its brevity comes at the cost of the details an agent needs.

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 one-parameter read-only lookup with rich annotations and no output schema, the definition is minimally workable. It still leaves the agent guessing about match semantics, result volume, and how results differ from geocode output.

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?

The single 'query' parameter has 0% schema description coverage, so the schema carries no meaning at all and the description must compensate. It only implies the query is a place name; it says nothing about whether mountain names, feature types, or partial strings are valid input.

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 fragment pairs a specific verb ('Search') with a concrete resource set - place names, localities, mountains, geographic features - so an agent can tell it is a geographic name lookup. It stops short of distinguishing itself from overlapping siblings such as geocode, identify_location, or search_stations, which also take a free-text location query.

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?

There is no when-to-use guidance, no exclusion, and no named alternative. With geocode and identify_location in the sibling list, an agent has no basis in the description for choosing this tool over those, which is a real routing gap.

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

Deploy Server

Other Tools