Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Check Detection

check_detection

Runs a stealth self-test against bot-detection services before sensitive navigation, optionally adding creepjs checks when deep is enabled and returning a verdict.

Instructions

Stealth self-test: sannysoft (~7s) + creepjs if deep (~40s). Before sensitive nav.

Ex: check_detection() → {"sannysoft":{"passed":31,"failed":0,...},"verdict":"good"} Ex: check_detection(deep=True) → {...,"creepjs":{"detected_headless":0,"stealth":0},"verdict":"good"}

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_detection"
  }
}

Input Schema

NameRequiredDescriptionDefault
deepNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a good job disclosing runtime expectations (~7s versus ~40s with deep) and what deep changes. The examples also preview the verdict-oriented output. It still omits prerequisites such as whether an active browser session is required and whether the check has any side effects.

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: it states the core behavior, timing, and usage context in one sentence, followed by two useful examples. Every element earns its place.

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 simple one-parameter tool with an output schema, the description is complete enough to call correctly: it explains deep behavior, timing, usage context, and example outputs. Missing sibling comparisons are minor given the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for the single 'deep' parameter, but the description fully explains its effect: enabling deep adds creepjs and increases runtime to about 40 seconds. The example with deep=True reinforces this meaning.

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 states a specific function: a stealth self-test using sannysoft and, when deep, creepjs. It also frames the purpose as a pre-sensitive-navigation check, making the tool clearly distinct in practical use. It does not explicitly contrast itself with sibling stealth/session tools such as cloak_status or rotate_fingerprint, so it falls just short of full sibling differentiation.

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?

The phrase 'Before sensitive nav' gives clear usage context and tells the agent when this check is appropriate. The deep example clarifies the optional path, but there is no explicit guidance on when not to use it or which sibling tools are alternatives.

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