Skip to main content
Glama

identify_location

Retrieve geographic features and data layers for any Swiss location using coordinates. Access transport, weather, geodata, and other open datasets without API keys.

Instructions

Identify geographic features and data layers at a specific Swiss location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lngYesLongitude (WGS84)
layersNoComma-separated layer ids (default: all visible)

Implementation Reference

  • The handler implementation for the identify_location tool in src/modules/geodata.ts.
    case "identify_location": {
      const lat = args.lat as number;
      const lng = args.lng as number;
      const extent = `${lng - 0.001},${lat - 0.001},${lng + 0.001},${lat + 0.001}`;
      const layers = args.layers ? `all:${args.layers}` : "all";
      const url = buildUrl(`${BASE}/rest/services/all/MapServer/identify`, {
        geometry: `${lng},${lat}`,
        geometryType: "esriGeometryPoint",
        layers,
        mapExtent: extent,
        imageDisplay: "500,500,96",
        tolerance: 5,
        sr: 4326,
        returnGeometry: false,
      });
      const data = await fetchJSON<IdentifyResponse>(url);
      return JSON.stringify({
        count: data.results.length,
        results: data.results.slice(0, 20).map(slimIdentifyResult),
      });
    }
  • The tool registration and input schema for identify_location.
      name: "identify_location",
      description: "Identify geographic features and data layers at a specific Swiss location",
      inputSchema: {
        type: "object",
        required: ["lat", "lng"],
        properties: {
          lat: { type: "number", description: "Latitude (WGS84)" },
          lng: { type: "number", description: "Longitude (WGS84)" },
          layers: { type: "string", description: "Comma-separated layer ids (default: all visible)" },
        },
      },
    },
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 states the tool 'identifies' features and layers, which suggests a read-only operation, but doesn't clarify permissions, rate limits, data sources, or response format. For a tool with no annotations and no output schema, this leaves significant gaps in understanding how it behaves.

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 communicates 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. It doesn't explain what 'identify' entails (e.g., returns a list, details format), data sources, or error handling. For a tool with 3 parameters and no structured behavioral hints, more context is needed to guide effective use.

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 input schema already documents all parameters (lat, lng, layers) with clear descriptions. The description adds no additional parameter semantics beyond implying Swiss location scope. This meets the baseline of 3, as the schema does the heavy lifting.

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: 'Identify geographic features and data layers at a specific Swiss location.' It specifies the verb ('identify'), resource ('geographic features and data layers'), and scope ('Swiss location'). However, it doesn't explicitly differentiate from sibling tools like 'geocode' or 'reverse_geocode' that might also handle location data, though the focus on features/layers is distinct.

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. It doesn't mention prerequisites (e.g., coordinate format), exclusions, or comparisons to siblings like 'get_weather' or 'get_snow_conditions' that might provide related geographic data. Usage is implied only by the tool's name and description.

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