Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

elevation

Get the altitude above sea level for one or more latitude/longitude coordinates. Accepts pipe-separated lat,lng pairs.

Instructions

Get the elevation (altitude above sea level in metres) for one or more lat/lng points.

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": {
      "locations": "<locations>"
    },
    "name": "elevation"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationsYesPipe-separated lat,lng points. e.g. '28.55,77.20|19.07,72.87' (Delhi and Mumbai)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states the basic operation, lacking details on limits, precision, data sources, or error handling. This is a minor gap for a simple tool.

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

Conciseness5/5

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

The single-sentence description is direct and efficient, with no unnecessary words. It front-loads the verb 'Get' and specifies the resource and unit.

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

Completeness4/5

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

For a simple elevation lookup with one parameter, the description is mostly complete. Minor omissions (e.g., maximum number of points) prevent a perfect score, but no output schema reduces the need for extensive details.

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 coverage is 100% with a detailed example for the 'locations' parameter. The description adds the phrase 'one or more', but adds no meaning beyond the schema. Baseline 3 is appropriate.

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 description clearly states the tool's purpose: retrieving elevation in metres for one or more lat/lng points. It specifies the unit (metres) and input structure, distinguishing it clearly from sibling tools like geocode or directions.

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

Usage Guidelines3/5

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

The description implies use for elevation queries but does not provide explicit guidance on when to use this tool versus alternatives. No siblings directly compete, but context like max points or rate limits is omitted.

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

Deploy Server

Other Tools