Skip to main content
Glama
deenesjakoruzh
Francis235

AMap MCP Server

by Francis235
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Non-official AMap Model Context Protocol (MCP) server that enables interaction with AMap powerful location related service. You can use in the following MCP clients like Cursor, Claude Desktop, Cline , Windsurf and other Client.

Prerequisite

  1. python 3.10+;

  2. Get your AMAP_KEY from AMAP open platform.

  3. Install uv (Python package manager), install with pip install uv or see the uv repo for additional install methods.

Related MCP server: MCP Python Server — API Wrapper

Quickstart with Cursor

Go to Cursor -> Cursor Settings -> MCP, click Add new global MCP server, and mcp.json will open, paste the following config content:

"AMap": {
        "command": "uvx",
        "args": [
          "amap-mcp"
        ],
        "env": {
          "AMAP_KEY": "<insert-your-AMap-here>"
        },
      },

Example usage

A demonstration video: Demo

Available Tools

1 tool
query_weatherB

The weather service of Amap. Query the weather of a given city.

Args:
    city (str): The city to query the weather.
ParametersJSON Schema
NameRequiredDescriptionDefault
cityYes

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the service provider ('Amap') but fails to describe key traits such as rate limits, authentication needs, error handling, or what the response format looks like. For a query tool with zero annotation coverage, this is a significant gap in transparency.

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 description is appropriately sized and front-loaded, with the core purpose stated first followed by parameter details. Both sentences earn their place by providing essential information without redundancy. The structure is clear and efficient for a simple tool.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate but lacks completeness. It covers the basic purpose and parameter but omits details on response format, error cases, and service constraints. For a query tool, this leaves gaps in understanding how to interpret results.

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?

The description adds meaningful context for the single parameter 'city' by specifying it as 'The city to query the weather,' which clarifies its role beyond the schema's basic title. With 0% schema description coverage and only one parameter, this adequately compensates, though it could detail format expectations (e.g., city names, language).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 as 'Query the weather of a given city,' specifying the verb 'query' and resource 'weather' with the target 'city.' It distinguishes the service provider as 'Amap,' but since there are no sibling tools, full differentiation isn't needed. However, it could be more specific about what weather data is returned.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It only states the basic function without context about availability, accuracy, or when it might fail. With no sibling tools, explicit alternatives aren't required, but general usage context is missing.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on weather queries.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (query_weather), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and descriptive.

Tool Count2/5

One tool is too few for a server named 'AMap MCP Server', which suggests a broader mapping or location service domain. A single weather query tool feels thin and incomplete for this apparent scope.

Completeness1/5

The server is severely incomplete for a mapping service domain. There are obvious gaps such as geocoding, routing, place search, or map display tools. The single weather tool does not provide meaningful coverage of the expected functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Francis235/amap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server