Skip to main content
Glama

Aquedra Run

Transform GeoJSON

transform_geojson

Applies one operation to a GeoJSON (buffer, simplify, centroid, bbox, convex_hull or clean) and returns the resulting GeoJSON. To measure areas or lengths use measure_geojson, and to change the CRS use reproject_geojson. Takes up to 50,000 features and 200,000 vertices and 1 MiB of arguments, and buffer takes up to 1,000 features and 4,000 vertices (5,000 and 20,000 with max_seconds over 3). 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>",
      "operation": "<operation>"
    },
    "name": "transform_geojson"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
operationYesOperation: buffer, simplify, centroid, bbox, convex_hull, or clean (drops point features with empty, non-numeric, swapped, out-of-range or 0,0 coordinates).
distance_mNoBuffer distance in meters (0 to 100000). Required for buffer. Buffer accepts at most 1,000 features, 4,000 vertices and 1,000 MultiPoint positions; with max_seconds above 3 (extended time), 5,000 features, 20,000 vertices and 5,000 MultiPoint positions.
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.
tolerance_mNoSimplify tolerance in meters, converted to degrees approximately (1 degree is about 111,320 m), so it is less exact away from the equator. Defaults to 10.
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.8/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses input ceilings, per-operation limits for buffer (1,000 features / 4,000 vertices, higher on the extended lane), the 1 MiB argument cap, per-unit pricing and when charges apply, that invalid input is never charged, that extended time holds the full amount up front and refunds unused seconds, and exactly which failures keep the charge versus refund in full. The annotations (destructiveHint=false, openWorldHint=false) are consistent with a compute-only operation that returns a new GeoJSON, and the description adds the credit-spending behavior the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and sibling routing are front-loaded in the first two clauses, which is the right order. The final sentence is a long run-on packing pricing, charging and refund exceptions into one breath, which is dense but largely unavoidable given how many distinct charge scenarios exist; slight trimming of repeated limit numbers would improve it.

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 7-parameter compute tool with nested geojson input, an output schema already present, and a non-trivial credit model, the description covers limits, error codes (422, 413, 499, 402), cost control and time budgeting. An agent has everything needed to call it safely without overspending.

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 the baseline is 3; the description earns above that by explaining parameter interactions the schema documents only in isolation — buffer's feature/vertex limits change with max_seconds, and max_seconds above 3 moves the call to a separate lane with different pricing. It does not restate distance_m or tolerance_m semantics, which is fine since the schema covers them fully.

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 ('Applies one operation to a GeoJSON ... returns the resulting GeoJSON'), enumerates the six operations, and explicitly names the siblings that handle the cases this tool does not (measure_geojson, reproject_geojson). An agent can distinguish it from those siblings without opening any 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?

Gives explicit when-to-use-elsewhere routing ('To measure areas or lengths use measure_geojson, and to change the CRS use reproject_geojson') plus concrete decision guidance for dry_run ('Set dry_run to true to get the price') and max_cost_usd ('to refuse a call that would cost more'). The extended-time escape hatch ('for heavier inputs set max_seconds from 4 to 30') tells the agent what to do when the default limits are hit.

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