Skip to main content
Glama

generate_pin_map

Read-only

Create a point map to visualize the location and distribution of points of interest (POIs) on a map. Use keywords to search for POIs and display their geographic data.

Instructions

Generate a point map to display the location and distribution of point data on the map, such as the location distribution of attractions, hospitals, supermarkets, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe map title should not exceed 16 characters. The content should be consistent with the information the map wants to convey and should be accurate, rich, creative, and attractive.
dataYesA list of keywords for the names of points of interest (POIs) in Chinese. These POIs usually contain a group of places with similar locations, so the names should be more descriptive, must adding attributives to indicate that they are different places in the same area, such as "北京市" is better than "北京", "杭州西湖" is better than "西湖"; in addition, if you can determine that a location may appear in multiple areas, you can be more specific, such as "杭州西湖的苏堤春晓" is better than "苏堤春晓". The tool will use these keywords to search for specific POIs and query their detailed data, such as latitude and longitude, location photos, etc. For example, ["西安钟楼", "西安大唐不夜城", "西安大雁塔"].
markerPopupNoMarker type, one is simple mode, which is just an icon and does not require `markerPopup` configuration; the other is image mode, which displays location photos and requires `markerPopup` configuration. Among them, `width`/`height`/`borderRadius` can be combined to realize rectangular photos and square photos. In addition, when `borderRadius` is half of the width and height, it can also be a circular photo.
widthNoSet the width of map, default is 1600.
heightNoSet the height of map, default is 1000.

Implementation Reference

  • Handler logic that identifies generate_pin_map as a map chart and executes generateMap to produce the output.
    const isMapChartTool = [
      "generate_district_map",
      "generate_path_map",
      "generate_pin_map",
    ].includes(tool);
    
    if (isMapChartTool) {
      // For map charts, we use the generateMap function, and return the mcp result.
      const { metadata, ...result } = await generateMap(tool, args);
      return result;
    }
  • Helper function that sends the generate_pin_map tool call and input to the external visualization service API.
     */
    export async function generateMap(
      tool: string,
      input: unknown,
    ): Promise<ResponseResult> {
      const url = getVisRequestServer();
    
      const response = await axios.post(
        url,
        {
          serviceId: getServiceIdentifier(),
          tool,
          input,
          source: "mcp-server-chart",
        },
        {
          headers: {
            "Content-Type": "application/json",
          },
        },
      );
      const { success, errorMessage, resultObj } = response.data;
    
      if (!success) {
        throw new Error(errorMessage);
      }
      return resultObj;
    }
  • Zod schema defining the input parameters for the generate_pin_map tool.
    const schema = {
      title: MapTitleSchema,
      data: POIsSchema,
      markerPopup: z
        .object({
          type: z.string().default("image").describe('Must be "image".'),
          width: z.number().default(40).describe("Width of the photo."),
          height: z.number().default(40).describe("Height of the photo."),
          borderRadius: z
            .number()
            .default(8)
            .describe("Border radius of the photo."),
        })
        .optional()
        .describe(
          "Marker type, one is simple mode, which is just an icon and does not require `markerPopup` configuration; the other is image mode, which displays location photos and requires `markerPopup` configuration. Among them, `width`/`height`/`borderRadius` can be combined to realize rectangular photos and square photos. In addition, when `borderRadius` is half of the width and height, it can also be a circular photo.",
        ),
      width: MapWidthSchema,
      height: MapHeightSchema,
    };
  • Tool registration metadata including name, description, and reference to inputSchema.
    const tool = {
      name: "generate_pin_map",
      description:
        "Generate a point map to display the location and distribution of point data on the map, such as the location distribution of attractions, hospitals, supermarkets, etc.",
      inputSchema: zodToJsonSchema(schema),
      annotations: {
        title: "Generate Pin Map",
        readOnlyHint: true,
      },
    };
  • src/server.ts:66-68 (registration)
    MCP server listTools handler that registers all chart tools (including generate_pin_map) for discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getEnabledTools().map((chart) => chart.tool),
    }));
Behavior3/5

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

Annotations indicate readOnlyHint=true, suggesting a safe read operation, which aligns with the description's 'generate' action implying creation of a map without destructive effects. The description adds some context about data processing ('search for specific POIs and query their detailed data') and marker modes, but doesn't cover rate limits, authentication needs, or output format. With annotations covering safety, the description provides moderate additional behavioral insight.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core purpose. It avoids unnecessary details, though it could be slightly more structured by separating examples. Every word contributes to understanding the tool's function without redundancy.

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 moderate complexity (5 parameters, nested objects, no output schema) and rich schema coverage, the description is adequate but lacks depth. It doesn't explain the output (e.g., map format, how results are returned) or error handling. With annotations covering safety, it meets minimum viability but misses opportunities to clarify usage scenarios or integration 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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal semantic value beyond the schema, mentioning 'point data' and examples like 'attractions', but doesn't explain parameter interactions or usage nuances. Baseline 3 is appropriate as the schema handles most documentation, though the description could enhance understanding of data parameter context.

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: 'Generate a point map to display the location and distribution of point data on the map, such as the location distribution of attractions, hospitals, supermarkets, etc.' This specifies the verb ('generate'), resource ('point map'), and scope ('point data'), distinguishing it from sibling tools like generate_district_map or generate_path_map. However, it doesn't explicitly differentiate from all siblings, as some might also involve maps.

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. It mentions examples like 'attractions, hospitals, supermarkets' but doesn't specify when to choose this over other map tools (e.g., generate_district_map) or chart tools. There's no mention of prerequisites, exclusions, or specific contexts for application.

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

Install Server

Other Tools

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/antvis/mcp-server-chart'

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