Skip to main content
Glama

get_my_location

Retrieve your current geographic location using your IP address to determine position data.

Instructions

Get the location of the current IP address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_my_location': checks tool name, calls ipfind.apiRequest.getMyLocation(), handles error, returns JSON response.
    if (request.params.name === "get_my_location") {
      const output = await ipfind.apiRequest.getMyLocation();
    
      if (!output) {
        throw new Error("Failed to fetch my location.");
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(output, null, 2),
          },
        ],
      };
    }
  • src/index.ts:60-67 (registration)
    Registration of 'get_my_location' tool in ListToolsRequestSchema handler, including name, description, and empty input schema.
    {
      name: "get_my_location",
      description: "Get the location of the current IP address",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper method in APIRequest class that performs the actual API call to retrieve the current IP location using the /me endpoint.
    async getMyLocation(): Promise<IPFindIPResponse> {
      return await this.makeRequest<IPFindIPResponse>(`/me?auth=${this.apiKey}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation but doesn't disclose rate limits, authentication needs, accuracy limitations, or what 'location' entails (e.g., coordinates, city). The agent lacks context on reliability or constraints.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy for an agent to parse quickly without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete for a location-fetching tool. It doesn't explain return values (e.g., format, data fields), potential errors, or behavioral nuances like IP-based limitations, leaving the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param details, but this is appropriate given the empty schema, meeting the baseline for tools without parameters.

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 with a specific verb ('Get') and resource ('location of the current IP address'). It distinguishes from sibling 'get_ip_location' by specifying 'current IP address' rather than a general IP lookup, though it doesn't explicitly contrast with 'get_api_usage'.

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 like 'get_ip_location' or 'get_api_usage'. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on tool names alone.

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

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