Skip to main content
Glama
Sign In
mcp-map-server

mcp-map-server

by ganyu123456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

map_search_poi

Search for POIs by keyword and optionally by city. Returns name, address, coordinates, and phone number.

Instructions

关键字 POI 搜索：按关键字搜索地点（如'星巴克'、'医院'），可限定城市。返回名称、地址、坐标、电话等。

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": {
      "keyword": "<keyword>"
    },
    "name": "map_search_poi"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo可选，限定城市名，如'上海'
pageNo页码，从 1 开始
limitNo每页数量（最多 20）
keywordYes搜索关键字，如'肯德基'、'加油站'
platformNoMap platform to use. Defaults to 'amap'.amap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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. It mentions return fields (name, address, coordinates, phone) but does not disclose important behavioral traits like rate limits, authentication needs, or pagination behavior beyond schema defaults. Missing idempotency or destructive hints.

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 a single, front-loaded sentence that efficiently conveys purpose and return information without unnecessary words.

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?

Given the absence of an output schema, the description compensates by listing key return fields. Combined with the schema's parameter descriptions, an agent has sufficient context to invoke the tool correctly, though additional details like result ordering could improve completeness.

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 parameter descriptions. The description adds no new semantic information beyond the schema; it only restates the city filtering capability. Baseline score of 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 it is a keyword POI search, provides concrete examples ('星巴克', '医院'), and notes city filtering. It distinguishes from sibling tools like map_search_around (location-based) and map_geocode (address conversion).

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 usage for keyword-based place searches but provides no explicit guidance on when to use it over siblings such as map_search_around or map_geocode. No when-not or alternative tool mentions.

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