Skip to main content
Glama
Sign In
Tengu

Tengu

by rfunix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_anonymity

Detect IP exposure, DNS leaks, and suspicious proxy headers to assess anonymity. Get actionable recommendations to strengthen your privacy.

Instructions

Check current anonymity level — IP exposure, DNS leaks, proxy headers.

Returns: Dictionary with real_ip_exposed, dns_leak_detected, anonymity_level, and recommendations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_anonymity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses output fields but does not mention safety behavior, side effects, or external network calls. This leaves the agent uncertain whether the tool makes outbound requests or is strictly local.

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?

Two sentences, clear structure, and no redundant text. The output description adds useful details without bloat.

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

Completeness4/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, the description explains the check scope and return values. It could mention prerequisites or usage context, but for this simple tool it is largely complete.

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?

There are zero parameters, so the description inherently cannot add parameter meanings. The baseline of 4 applies due to no parameters.

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 uses a specific verb 'Check' and identifies the resource 'current anonymity level', specifying IP exposure, DNS leaks, and proxy headers. It clearly distinguishes from sibling tools like proxy_check and tor_check by focusing on the overall anonymity assessment.

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?

There is no explicit guidance on when to use this tool versus alternatives, such as proxy_check or tor_check. The description implies its usage but does not state scenarios, exclusions, or conditions.

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

Deploy Server

Other Tools