Skip to main content
Glama

Local Public Ip

local_public_ip

Get your machine's public IP from external services like ipify and icanhazip, with automatic fallback. Verify NAT, VPN, or proxy setup without admin rights.

Instructions

Get the public IP address of the local machine.

Queries external services (ifconfig.me, ipify, icanhazip) in turn until one answers, identifying itself with the net-mcp User-Agent. Useful for verifying NAT, VPN, or proxy configuration. Does not require admin privileges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoAdditional context about the result
errorNoWhy the tool could not produce a result: input validation failure, tool disabled by configuration, binary not installed, or no service answered. Empty when the command executed.
stderrYesStandard error of the command, or the failure message when the command did not run
stdoutYesStandard output of the command (curl output is capped at 10,000 characters)
commandYesThe exact command line that was executed, or the tool name if the command never ran
successYesTrue when the command ran and exited with status 0
platformYesOperating system the command ran on (Darwin, Linux or Windows)
returncodeYesProcess exit status. 0 = success; 2 = input rejected before running; 124 = timed out; 126 = disabled by config or permission denied; 127 = binary not found

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full disclosure burden and does so well. It reveals outbound queries to three external services, the fallback sequencing, the User-Agent used, and the privilege requirement.

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 compact and front-loaded: purpose first, then external behavior, use cases, and privilege note. Every sentence adds useful information with no redundancy.

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

Completeness5/5

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

For a zero-parameter tool with an output schema present, the description is complete enough. It covers side effects, fallback behavior, use cases, and requirements; return-format details are handled by the output schema.

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, so there is no parameter semantics to document. The description focuses on the operation and return intent, which is sufficient for this no-input tool.

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's action and scope: getting the public IP address of the local machine. This distinguishes it from sibling tools like local_interfaces (local addresses) and other network diagnostic tools.

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?

It provides concrete use cases: verifying NAT, VPN, or proxy configuration, and notes that no admin privileges are required. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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