Mithwire MCP

session_warmup

Build a natural browsing footprint by visiting curated or custom sites to accumulate cookies, localStorage, and history, reducing bot signals from fresh profiles.

Instructions

Warm a browser session by visiting sites to accumulate realistic browsing state (cookies, localStorage, history). A fresh profile with no history is a strong bot signal; this tool builds a natural footprint. Uses a curated site list by default; pass sites= to override. geo_region filters the built-in list to a country code (e.g. "US", "GB", "DE") plus global sites.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "session_warmup"
  }
}

Input Schema

Name	Required	Description	Default
`sites`	No
`visits`	No
`max_dwell`	No
`min_dwell`	No
`geo_region`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the mechanism and side effects (visits sites, accumulates cookies/localStorage/history, uses a curated list) but omits operational traits such as how long the warmup takes, whether it blocks, rate limits, or whether an active session is required.

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?

Front-loaded with purpose, then rationale, then default/override behavior in four tight sentences. No filler, though the geo_region sentence is slightly dense and could be split.

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?

An output schema exists, so return values need no explanation, and the description adequately frames the tool's intent. However, for a 6-parameter, annotation-free state-mutating tool it should say more about timing, required session state, and the remaining dwell/visits parameters.

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?

Schema coverage is 0% across 6 parameters, so the description must compensate. It adds real meaning for sites (override of the curated default) and geo_region (country code plus global sites, with examples), but leaves visits, max_dwell, min_dwell, and session_id entirely unexplained.

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?

States a specific verb+resource ('Warm a browser session by visiting sites') and explains the concrete effect (accumulating cookies, localStorage, history). It is clearly distinguishable from siblings like browser_navigate or session_start because it describes the footprint-building purpose, not just navigation.

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?

Gives a clear rationale for when this matters ('A fresh profile with no history is a strong bot signal; this tool builds a natural footprint'), which implies usage before navigation. It also explains the default curated list versus the sites= override, but names no explicit alternative tool or exclusion condition.

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

Deploy Server