IP Find
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPFIND_API_KEY | Yes | Your IP Find API key, which can be generated at IPfind.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ip_locationC | Get the location of an IP address |
| get_my_locationB | Get the location of the current IP address |
| get_api_usageC | Get the usage of the API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_api_usage monitors API usage, get_ip_location finds the location of a specified IP, and get_my_location finds the location of the current IP. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with the prefix 'get_' and descriptive nouns (api_usage, ip_location, my_location). This makes the tools predictable and easy to understand.
With 3 tools, the server is well-scoped for IP location and API usage tracking. Each tool serves a clear, non-redundant function, making the count appropriate for the domain.
The tools cover core IP location queries (for specified and current IPs) and API usage monitoring, which are essential for the server's purpose. A minor gap might be the lack of tools for bulk IP lookups or historical data, but the basic functionality is complete.