Skip to main content
Glama

Aquedra Run

Reproject GeoJSON

reproject_geojson

Reprojects every coordinate of a GeoJSON from one CRS to another (EPSG:4326, 3857, 4674, 5361, 32718, 32719 or a WGS84 UTM zone) and returns the GeoJSON. To convert individual points to degrees-minutes-seconds or UTM text use convert_coordinates, and to read a CSV, KML, GPX or Shapefile use convert_geo_file. Takes a GeoJSON of up to 50,000 features and 200,000 vertices, and up to 1 MiB of arguments. Costs US$0.001 per unit (up to 1,000 features and 10,000 vertices) 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": {
      "geojson": "<geojson>",
      "from_crs": "<from_crs>",
      "to_crs": "<to_crs>"
    },
    "name": "reproject_geojson"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_crsYesCRS to convert the coordinates to, as EPSG:<n>.
dry_runNoWhen true, return the price (cost_usd) and units of this call without running it or charging anything.
geojsonYesGeoJSON object: a FeatureCollection, a Feature or a bare geometry, in WGS84 longitude/latitude unless a CRS is stated. Limits: 50,000 features and 200,000 vertices. An operation that runs past its compute or memory limit fails with 422 operation_too_complex or operation_too_large.
from_crsYesCRS of the input coordinates, as EPSG:<n>.
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 give the generic readOnly/destructive/openWorld flags, so the description carries real weight here and does: it discloses the billing model (US$0.001 per unit), that 3 s is charged only on success, that invalid input is never charged, that extended time is held up front and partially refunded, and which error codes (422 operation_too_complex / operation_too_large, 413, 499, 402) retain or refund the charge. That is behavior an agent cannot infer anywhere else.

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?

The purpose is front-loaded in the first clause, but the body is one very long sentence that largely duplicates the max_seconds, dry_run and max_cost_usd schema descriptions verbatim. The pricing/refund rules are genuinely useful, yet repeating the schema's own text costs readability without adding information.

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 paid, computationally bounded tool with a nested GeoJSON object, an output schema, and 6 parameters, the description covers scale limits, cost, failure modes and refund behavior. With an output schema present it reasonably omits describing the returned GeoJSON structure.

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 description coverage is 100%, so the baseline is 3; the description earns above that by enumerating acceptable CRS values (EPSG:4326, 3857, 4674, 5361, 32718, 32719 or a WGS84 UTM zone), which the schema's EPSG pattern alone cannot convey. It still mostly restates the dry_run and max_cost_usd semantics already spelled out in 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 and resource (reproject every coordinate of a GeoJSON between two CRSs) plus the return value, and names the supported CRS set. It also distinguishes itself from convert_coordinates (DFS/UTM text) and convert_geo_file (CSV/KML/GPX/Shapefile), so an agent can pick it without opening a 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?

Explicit when-to-use guidance with named alternatives and the condition selecting each: use convert_coordinates for point-to-text conversion, convert_geo_file for file formats. It also gives the when-not-to-use via input limits (50,000 features / 200,000 vertices / 1 MiB of arguments) that force a different route.

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