Skip to main content
Glama

search_places

Find Swiss locations, mountains, and geographic features by name using Swiss open data. Search place names to get accurate geographic information without API keys.

Instructions

Search Swiss place names, localities, mountains, and geographic features

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPlace name to search
typeNoType filter: locations, featuresearch

Implementation Reference

  • The handler logic for "search_places" inside handleGeodata in src/modules/geodata.ts.
    case "search_places": {
      const url = buildUrl(`${BASE}/rest/services/api/SearchServer`, {
        searchText: args.address as string ?? args.query as string,
        type: args.type as string ?? "locations",
        sr: 4326,
        limit: 10,
      });
      const data = await fetchJSON<SearchResponse>(url);
      return JSON.stringify({
        count: data.results.length,
        results: data.results.map(slimSearchResult),
      });
  • The input schema definition for "search_places" in src/modules/geodata.ts.
    {
      name: "search_places",
      description: "Search Swiss place names, localities, mountains, and geographic features",
      inputSchema: {
        type: "object",
        required: ["query"],
        properties: {
          query: { type: "string", description: "Place name to search" },
          type: { type: "string", description: "Type filter: locations, featuresearch" },
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the search scope but fails to describe critical traits like whether this is a read-only operation, any rate limits, authentication needs, or what the output format might be (e.g., list of results with details). For a search tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly states what the tool does, making it easy to parse and understand quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a search tool. It doesn't explain what the tool returns (e.g., structured data, error handling), behavioral constraints, or how it differs from siblings. This leaves the agent with insufficient context to use it effectively beyond basic parameter input.

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?

The input schema has 100% description coverage, clearly documenting the 'query' and 'type' parameters. The description adds no additional semantic details beyond what the schema provides, such as examples of valid 'type' values or search syntax. With high schema coverage, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose as searching for Swiss place names, localities, mountains, and geographic features, which is a specific verb ('search') with a well-defined resource scope. However, it does not explicitly differentiate from sibling tools like 'geocode' or 'identify_location', which might have overlapping geographic functions, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'geocode' for coordinate-based lookups or 'identify_location' for reverse geocoding. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server