Detect VPN usage
detect_vpnRead-only
Detect whether an IP address is using a VPN.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ip_address | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
screening
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, which covers the safety profile. The description adds no behavioral context beyond the title—no mention of how detection works, limitations, or data sources. It restates the purpose without revealing any extra behavioral traits.
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, concise sentence that front-loads the action and target. Every word earns its place, with no redundancy or unnecessary detail. It is an ideal length for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool shape—one parameter, readOnlyHint annotation, and an output schema—the description is minimally adequate. However, it lacks usage differentiation and parameter detail, which are important for an AI agent selecting among sibling tools. The missing guidance prevents a higher score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one parameter (ip_address) with no description, and schema description coverage is 0%. The description mentions 'IP address' but provides no format, constraints, or example. The parameter name is self-explanatory, so the description adds minimal value beyond what the schema name already conveys.
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 uses a specific verb 'detect' and clearly identifies the resource: whether an IP address is using a VPN. It is distinct from sibling tools like geolocate_ip, though it doesn't explicitly say so. The purpose is immediately clear.
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?
No explicit guidance is given on when to use this tool vs. alternatives. The description implies 'use to check VPN status for an IP', but there are no exclusions, prerequisites, or comparisons to related tools like geolocate_ip. The context is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a unique entity type: IP, country, crypto address, email, government ID, PEP, and website. The two IP-related tools (detect_vpn and geolocate_ip) are distinct in purpose and clearly named. No two tools overlap in what they screen.
Naming Consistency4/5
The eight screen_* tools follow a consistent verb_noun pattern (e.g., screen_email, screen_website). The two IP tools (detect_vpn, geolocate_ip) use different verbs, creating minor inconsistency but still understandable given their unique actions.
Tool Count5/5
With 8 tools, the server is well-scoped for a sanctions/anti-crime screening service. Each tool addresses a distinct screening domain, and the count is neither too thin nor bloated.
Completeness4/5
The tool set covers a wide range of entity types: IPs, countries, crypto, email, government IDs, PEPs, and websites. A minor gap exists for phone numbers or other entity types, but the primary screening workflows are well-covered and usable without workarounds.