Skip to main content
Glama

Convert LV95 → WGS84

convert_lv95_to_wgs84
Read-only

Convert Swiss LV95 coordinates (EPSG:2056) to WGS84 latitude/longitude, auto-detect legacy LV03 values, and reject swapped or out-of-range inputs with an explanation.

Instructions

Convert Swiss LV95 coordinates (EPSG:2056, easting ~2'600'000 / northing ~1'200'000) to WGS84 latitude/longitude. LV03 legacy values (600'000/200'000 range) are auto-detected and shifted. Swapped easting/northing and out-of-range values are rejected with an explanation.

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": {
      "easting": "<easting>",
      "northing": "<northing>"
    },
    "name": "convert_lv95_to_wgs84"
  }
}

Input Schema

NameRequiredDescriptionDefault
eastingYesLV95 easting (E, ~2'480'000–2'840'000) or LV03 easting (~480'000–840'000)
northingYesLV95 northing (N, ~1'070'000–1'300'000) or LV03 northing (~70'000–300'000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral detail: legacy LV03 values are automatically detected and shifted, and swapped or out-of-range inputs are rejected with an explanation rather than silently producing garbage. That rejection-with-explanation behavior is the key thing an agent needs to plan around.

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?

Three tight sentences, each carrying distinct information (purpose, coordinate ranges, legacy handling, error behavior), with the core purpose front-loaded. No filler.

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 conversion with no output schema, this covers inputs, edge cases, and failure modes well. The one gap is that it doesn't state the output convention (lat/lon order, decimal degrees, axis order), which matters for a geodetic conversion.

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 schema already documents both parameters including their valid ranges. The description reinforces the EPSG codes and adds the rejection rule for swapped axes, but adds no format or precision guidance beyond the schema.

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

Purpose5/5

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

States a specific verb (convert), a specific source CRS with EPSG code and typical value ranges, and a specific target (WGS84 latitude/longitude). This is unambiguously distinguishable from the reverse sibling convert_wgs84_to_lv95.

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?

The input conditions are well framed (LV95 values vs auto-detected LV03 values), which tells the agent when this tool applies. However, it never names the reverse tool or state when not to use this one, leaving the agent to infer that WGS84 input should go elsewhere.

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