Skip to main content
Glama

identify_location

Read-onlyIdempotent

Retrieves Swiss geographic features and swisstopo data layers for any WGS84 coordinates, helping you identify what exists at a specific latitude and longitude.

Instructions

Geographic features and swisstopo data layers at a location

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "identify_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lngYesLongitude (WGS84)
layersNoComma-separated layer IDs (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / layers / description
      Previous value: -"Comma-separated layer ids (default: all visible)"New value: +"Comma-separated layer IDs (default: all)"
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds nothing beyond that: it doesn't say what is returned per feature/layer, what happens with the default 'all layers', or how open-world external swisstopo queries behave (latency, coverage limits).

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 a single short fragment with no padding, so there is no wasted wording, but it is not front-loaded with a verb or outcome and reads as a label rather than an instruction. Brevity here reflects under-specification rather than disciplined conciseness.

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?

With no output schema and an open-world annotation, the description should convey what kinds of features/layers come back and how broad 'all layers' is. It leaves the agent unable to predict the result shape or to judge how this tool differs from the several map/geo siblings.

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%, with lat/lng documented as WGS84 and layers documented as comma-separated IDs defaulting to all, so the schema carries the parameter burden. The description contributes no additional meaning about parameter format, valid layer IDs, or coordinate constraints, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resources ('geographic features and swisstopo data layers') and implies a point lookup via 'at a location', but it is a bare noun phrase with no verb, so the operation itself is inferred from the tool name. It also fails to distinguish this from close siblings such as identify_map_layer, find_map_features, and reverse_geocode.

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 mention of when a sibling like reverse_geocode or find_map_features would be preferable, and no stated prerequisites. The only hint is the 'at a location' phrase implying a coordinate-based lookup.

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