maptiler_get_elevationLook up ground elevation at up to 50 coordinates. Returns an array of [lng, lat, elevation] triples. API: GET /elevation/{locations}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | Elevation unit. Default meters. | |
| locations | Yes | 1-50 [longitude, latitude] pairs (latitude -85..85). |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / locations / items / itemsPrevious value: -[
- {
- "maximum": 180,
- "minimum": -180,
- "type": "number"
- },
- {
- "maximum": 85,
- "minimum": -85,
- "type": "number"
- }
-]New value: +falseInput schema / properties / locations / items / maxItemsAdded value: +2Input schema / properties / locations / items / minItemsAdded value: +2Input schema / properties / locations / items / prefixItemsAdded value: +[
+ {
+ "maximum": 180,
+ "minimum": -180,
+ "type": "number"
+ },
+ {
+ "maximum": 85,
+ "minimum": -85,
+ "type": "number"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=true, so the description adds real value: it discloses the 50-coordinate cap, the exact return structure ([lng, lat, elevation] triples), and the underlying API path. It does not mention rate limits or error behavior, but for a simple read-only lookup this is solid disclosure beyond the structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, zero filler, with the core purpose and the return format front-loaded. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, and the description compensates by specifying the return shape and coordinate ordering. Combined with the readOnlyHint annotation and a fully documented schema, an agent has nearly everything needed to call and interpret this tool correctly; only rate-limit/pagination behavior is unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and both parameters (locations, unit) are already documented in the schema, including the lat/lng order and bounds. The description repeats the 50-coordinate limit without adding format or syntax detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Look up ground elevation') plus a scope constraint (up to 50 coordinates). The domain is unique among siblings (geocode, reverse_geocode, transform_coordinates), so an agent can identify it without confusion, though it never explicitly contrasts itself with any sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus alternatives, and no prerequisites or exclusions are stated. The description only says what it does and the API shape; all usage context must be inferred from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.