Skip to main content
Glama

Aquedra Run

Convert coordinates

convert_coordinates

Converts up to 1,000 points between decimal degrees (dd), degrees-minutes-seconds (dms) and UTM, and returns each point in the requested output formats, in the input order. To change the coordinate reference system of a GeoJSON use reproject_geojson. Takes up to 1,000 points per call (WGS84 latitude and longitude, or UTM zone, hemisphere, easting and northing). Costs US$0.001 per unit (up to 1,000 points) from prepaid credits; with the default 3 s it is charged only when it succeeds, and invalid input is never charged. Set dry_run to true to get the price without charging and max_cost_usd to refuse a call that would cost more; for heavier inputs set max_seconds from 4 to 30, where each second over the 3 included costs US$0.0005, the full time is held up front and the unused part refunded, and the price and the time used are charged if the call runs out of time or memory, or is cancelled while running.

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": {
      "from": "<from>",
      "to": "<to>",
      "points": "<points>"
    },
    "name": "convert_coordinates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesOutput formats to return for every point (1 to 3 of dd, dms, utm).
fromYesFormat of the input points: dd (decimal degrees), dms (degrees-minutes-seconds text) or utm.
pointsYesUp to 1000 points. Each is {lat, lon} for dd, a text for dms, or {zone, hemisphere, easting, northing} for utm, matching `from`.
dry_runNoWhen true, return the price (cost_usd) and units of this call without running it or charging anything.
max_secondsNoCompute time limit in seconds, 1 to 30 (default 3; 1 to 3 all use the standard 3 s). The price includes 3 s of compute. From 4 to 30 (extended time) the call runs on a separate lane, where buffer accepts larger inputs, and each second over 3 costs the geo_compute_second price: the price plus all those seconds is held at the start (that is what dry_run reports and max_cost_usd is compared with), the seconds not used are refunded, and the response adds compute_ms and max_seconds. With extended time the price and the time used are charged if the call runs out of time or memory, or is cancelled while running: 422 operation_too_complex keeps the whole hold, 422 operation_too_large or 413 result_too_large (a result over 8 MiB) or 499 cancelled keep the price and the seconds used, and those errors carry cost_usd. Any other failure is refunded in full.
max_cost_usdNoThe most this call may cost, in USD, as a number or decimal text with at most 6 decimals (e.g. 0.01 or "0.01"). A call that would cost more is refused with 402 max_cost_exceeded and nothing is charged.

Output Schema

NameRequiredDescriptionDefault
unitsYesPrice units the input measured.
resultNoThe operation's result; absent with dry_run.
call_idNoServer-issued id of the call; absent with dry_run.
dry_runNoTrue when nothing was run or charged.
cost_usdYesWhat the call cost (or would cost, with dry_run), US dollars as decimal text.
compute_msNoExtended time only: the compute time the call was billed on, in milliseconds.
balance_usdNoCredit balance after the charge, US dollars as decimal text; absent with dry_run.
max_secondsNoExtended time only: the max_seconds the call ran (or would run) with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the mutation/idempotency profile; the description goes far beyond by disclosing the pricing model ($0.001 per unit), the charge-on-success rule, refund behavior, and specific failure semantics (422 operation_too_complex keeps the whole hold, 402 max_cost_exceeded charges nothing, extended-time failures keep price plus seconds used). This is exactly the billing and failure context annotations cannot convey.

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?

Purpose is correctly front-loaded, but the billing section is a single run-on sentence packing four distinct policies, and the 1,000-point limit is stated twice (opening sentence and again as 'Takes up to 1,000 points per call'). The content is useful but could be structured into discrete sentences without losing meaning.

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

Completeness5/5

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

For a 6-parameter, cost-incurring compute tool with an output schema, this covers everything an agent needs to call it safely: limits, input-order guarantee, cost ceiling mechanism, timeout tradeoffs, and error-to-charge mapping. Return value shape is left to the output schema, which is the correct division of labor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the floor, and the description adds real value on top: it clarifies the interaction between max_seconds, the up-front hold, refunds, and what dry_run reports versus what max_cost_usd is compared against. It stops short of adding format syntax for the point payloads (e.g. the dms string grammar), leaving that entirely to 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?

The first sentence states a specific verb (converts), resource (points between dd/dms/utm), batch limit, and return ordering, and explicitly names the sibling it is not for (reproject_geojson when the goal is changing a GeoJSON CRS). An agent can distinguish this from transform_geojson or convert_geo_file without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit alternative with the selecting condition (use reproject_geojson to change a GeoJSON CRS) plus concrete routing within the tool itself: dry_run to price without charging, max_cost_usd to bound spend, and max_seconds 4-30 only for heavier inputs. The when-to-use surface is fully covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources