Skip to main content
Glama

Aquedra Run

Measure GeoJSON

measure_geojson

Measures the geodesic area, perimeter and length of each feature of a GeoJSON and returns them per feature with totals, in square meters and meters. To change the CRS use reproject_geojson, and to buffer, simplify or clean the geometry use transform_geojson. Takes a GeoJSON of up to 50,000 features and 200,000 vertices in WGS84 longitude and latitude, 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>"
    },
    "name": "measure_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.
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.5/5.0
Behavior5/5

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

Far beyond the annotations: it discloses input limits (50,000 features, 200,000 vertices, 1 MiB arguments), the credit-based pricing model with per-unit costs, that the default 3 s run is charged only on success, and the refund/charge rules for timeout, OOM and cancellation. The annotations say readOnlyHint=false, which is consistent with a tool that consumes prepaid credits, so there is no contradiction.

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?

Well front-loaded — purpose, then alternatives, then limits, then cost — but the closing sentence is a dense run-on covering holds, refunds, four error codes and extended-time pricing that largely restates the max_seconds schema. The pricing detail could be trimmed without losing decision-relevant 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 revenue-metered geometry tool with an output schema, it covers everything an agent needs: what is measured, which feature types get which measures, input ceilings, the cost model, how to avoid being charged, and the failure modes with their cost consequences.

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 every point the description makes about dry_run, max_cost_usd and max_seconds is also spelled out in the schema. The description adds only the interaction between them (quote via dry_run, then enforce via max_cost_usd), so baseline 3 is right when the schema carries the detail.

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?

Opens with a specific verb and resource: 'Measures the geodesic area, perimeter and length of each feature of a GeoJSON and returns them per feature with totals, in square meters and meters.' That distinguishes it immediately from reproject_geojson and transform_geojson, which are named in the next sentence.

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?

Explicitly routes the agent: 'To change the CRS use reproject_geojson, and to buffer, simplify or clean the geometry use transform_geojson.' It also gives when-to-use guidance for the cost-control parameters (dry_run for priced quotes, max_cost_usd to cap spend, max_seconds for heavier inputs), so both selection and parameter usage are 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