mcp-meituan-ip
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-ip-locC | 获取指定ip的大致位置与经纬度信息 |
| get-latlngC | 根据经纬度获取详细位置信息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| 美团IP查询工具 | 使用美团暴露的接口开发的IP与位置信息转换 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one maps IP addresses to locations, while the other maps latitude/longitude coordinates to detailed location information. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the input type.
Both tools follow a consistent verb_noun naming pattern with hyphens (get-ip-loc and get-latlng), using the same verb 'get' and descriptive nouns. This predictable structure enhances readability and usability.
With only two tools, the server feels thin for a location/geolocation service, as it lacks operations like reverse geocoding, batch processing, or error handling. While the tools are complementary, the scope is minimal and may limit agent workflows.
The server covers basic IP and coordinate lookups but has notable gaps, such as missing reverse geocoding from location to coordinates, validation tools, or support for multiple IPs. This could lead to agent workarounds or failures in more complex scenarios.