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

mcp-map-server

by ganyu123456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

map_ip_location

Locate the approximate city and province from an IP address. Leave blank to locate the source IP.

Instructions

IP 定位：根据 IP 地址返回其大致所在的省市。留空则定位请求来源 IP。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "map_ip_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNo可选，IP 地址；留空则定位调用方 IP
platformNoMap platform to use. Defaults to 'amap'.amap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The description covers basic behavior (returns province/city, default behavior) but lacks detail on error handling, accuracy, or platform differences. With no annotations, more transparency would be beneficial.

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?

Extremely concise at two sentences, no unnecessary words, and front-loaded with the main verb and resource.

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

Completeness2/5

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

Given no output schema, the description fails to specify the response format (e.g., fields for province and city), and does not mention error scenarios or limitations, leaving an agent under-informed.

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%, so the description adds only marginal value (e.g., clarifying the blank IP case). The baseline 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 the tool returns the approximate province and city based on an IP address, distinguishing it from sibling tools like map_direction or map_geocode that serve different purposes.

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

Usage Guidelines4/5

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

The description implicitly guides usage by explaining that leaving the IP blank locates the requester, but does not explicitly compare to alternatives or state when not to use.

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