Skip to main content
Glama

Convert WGS84 → LV95

convert_wgs84_to_lv95
Read-only

Convert WGS84 latitude and longitude for Switzerland to Swiss LV95 (EPSG:2056) coordinates and legacy LV03 values for mapping and geodata workflows.

Instructions

Convert WGS84 latitude/longitude (Switzerland and surroundings) to Swiss LV95 coordinates (EPSG:2056). Also returns legacy LV03 values.

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>",
      "lon": "<lon>"
    },
    "name": "convert_wgs84_to_lv95"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland ≈ 45.8–47.8)
lonYesWGS84 longitude (Switzerland ≈ 5.9–10.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds genuine beyond-schema behavior by disclosing that legacy LV03 values are also returned, which is return-value information not otherwise available since there is no output schema.

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?

Two short sentences with the target CRS and EPSG code front-loaded, then the secondary LV03 return noted last. Nothing is redundant and no sentence is 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 pure conversion with full schema coverage and no output schema, the description covers direction, domain, and the extra LV03 return values. It could still note the output shape (easting/northing ordering) or out-of-range behavior, but nothing essential for correct invocation is missing.

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% and both parameters already carry their Swiss coordinate ranges inline. The description restates the input as 'latitude/longitude' but adds no format, precision, or unit guidance beyond the schema, so baseline 3 applies.

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?

Names a specific verb (convert) plus an exact source CRS (WGS84 lat/lon) and target CRS (LV95, EPSG:2056), which cleanly separates it from the inverse sibling convert_lv95_to_wgs84. An agent can pick the correct direction from the name and first clause alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The geographic qualifier '(Switzerland and surroundings)' establishes the valid domain of use, which is meaningful context. It stops short of an explicit when-not statement or naming the reverse tool for out-of-domain inputs, so it sits just below the top band.

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