web-scraper-server

configure_stealth

Adjust stealth mode and robots.txt settings to prevent bot detection and comply with website scraping policies.

Instructions

Configure stealth mode and robots.txt compliance.

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": "configure_stealth"
  }
}

Input Schema

Name	Required	Description	Default
`stealth_mode`	No
`respect_robots`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.5Aug 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral transparency. It only says 'configure,' which implies a mutation, but it doesn't disclose whether settings persist, affect other tools, require permissions, or what the output looks like. This is a significant gap for a configuration tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that conveys the core purpose without wasted words. It is concise and well-structured, though it leaves out necessary details. This is appropriate conciseness but approaches under-specification.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has two optional boolean parameters and an output schema, the description is incomplete. It doesn't explain what stealth mode does, how robots.txt compliance is handled, or what the return value signifies. The lack of annotations and parameter descriptions leaves an agent without critical context for invoking and interpreting results.

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 provides two boolean parameters with defaults but no descriptions, and the tool description offers no parameter details. The names 'stealth_mode' and 'respect_robots' give some hints, but the description does not clarify what they control or their implications. Since schema description coverage is 0%, the description should compensate but doesn't.

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 clearly states the tool configures 'stealth mode and robots.txt compliance,' which is a specific resource. It uses the verb 'configure' and is distinguishable from sibling tools like 'configure_scraper' and 'configure_runtime' by focusing on stealth/robots settings. However, it doesn't elaborate on what stealth mode entails, so it's clear but not deeply detailed.

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 usage guidance is provided. The description does not mention when to use this tool, what scenarios call for stealth mode, or any exclusions. There are no references to alternative tools or conditions under which this configuration should be applied.

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

Deploy Server