Skip to main content
Glama
danilat
by danilat

google-maps-link

Generate Google Maps links from coordinates to locate tram stations and stops in Zaragoza.

Instructions

Get a Google Maps link from coordinates to help people to find a station o stop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes

Implementation Reference

  • Handler function that generates and returns a Google Maps URL from latitude and longitude coordinates.
    async ({ latitude, longitude }) => {
      const mapsUrl = `https://www.google.com/maps?q=${latitude},${longitude}`;
      return {
        content: [{ type: "text", text: mapsUrl }],
      };
    }
  • Input schema using Zod for latitude and longitude as numbers.
    {
      latitude: z.number(),
      longitude: z.number(),
    },
  • index.js:185-198 (registration)
    Registration of the 'google-maps-link' tool with server.tool, including description, schema, and inline handler.
    server.tool(
      "google-maps-link",
      "Get a Google Maps link from coordinates to help people to find a station o stop",
      {
        latitude: z.number(),
        longitude: z.number(),
      },
      async ({ latitude, longitude }) => {
        const mapsUrl = `https://www.google.com/maps?q=${latitude},${longitude}`;
        return {
          content: [{ type: "text", text: mapsUrl }],
        };
      }
    );
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 states the tool generates a link but doesn't describe what the link looks like (e.g., URL format, whether it opens in a browser), any rate limits, error handling, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded: the first part clearly states the core function. The additional context about helping find stations or stops is useful but could be more integrated. It avoids unnecessary words, though it could be slightly more structured for clarity.

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 the tool's simplicity (2 parameters, no output schema, no annotations), the description is incomplete. It lacks details on output format (e.g., what the link looks like), error cases, or usage constraints. For a tool that generates external links, more context on behavior and results would be helpful for an AI agent to use it effectively.

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?

The description mentions 'coordinates' but doesn't specify the parameters (latitude and longitude) or their semantics (e.g., decimal degrees, range constraints). With 0% schema description coverage, the description adds minimal value beyond implying coordinate input. It doesn't compensate for the coverage gap, but since there are only 2 parameters, the baseline is slightly higher than minimal.

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: 'Get a Google Maps link from coordinates' specifies the action (get) and resource (Google Maps link). It adds context about helping people find stations or stops, which clarifies the use case. However, it doesn't explicitly differentiate from sibling tools like 'geolocation-from-address', which serves a related but different purpose.

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 minimal usage guidance: it mentions helping people find stations or stops, which implies a navigation context. However, it doesn't specify when to use this tool versus alternatives (e.g., 'geolocation-from-address' for reverse geocoding) or any prerequisites like coordinate format. No explicit when-not or alternative guidance is given.

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/danilat/mcp-dndzgz'

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