Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_ipA

Run a LIVE network & abuse reputation check on an IP address or a domain name. Performs real DNS / DNSBL / reverse-DNS lookups (something an LLM cannot do on its own) and returns: geolocation (RIR country) + ASN/organisation + BGP prefix, reverse DNS (PTR), a network-TYPE deduction (datacenter/hosting, VPN/proxy, Tor exit, mobile/carrier, or residential ISP), DNS blocklist (DNSBL) membership, Tor-exit status, and a 0–100 abuse/risk score with a CLEAN / LOW_RISK / ELEVATED / HIGH_RISK verdict and explained findings. Use this to vet inbound traffic, validate signups/registrations, decide whether to challenge a request, or moderate user-supplied IPs/domains. Pass deep=true for more blocklists and richer reasons.

check_manyA

Run the live IP/domain reputation check on several targets at once (e.g. a list of IPs from your logs). Returns one concise verdict per target. Useful for batch-vetting traffic or a blocklist candidate set.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: check_ip handles single targets while check_many handles batch processing. Descriptions explicitly differentiate the use cases.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern: 'check' + target type (ip or many). Simple and predictable.

Tool Count3/5

Only 2 tools for IP/domain reputation checking feels thin. While the core functionality is covered, the server would benefit from additional tools for advanced features like whitelist management or historical queries.

Completeness4/5

The tool set covers the primary use case of live reputation checking for single and multiple targets. Minor gaps exist (e.g., no tool for checking URLs or managing blocklists), but the domain is simple and adequately served.

Maintenance

ActivityMaintained
ResponsivenessSyncing