Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Warm Session

warm_session

Pre-warm a browsing session with a plausible profile history before bot-detection-heavy targets to avoid zero-history flags during checkout.

Instructions

Pre-warm w/ plausible browsing (profile: general/shopping/news/minimal). Before bot-detection-heavy targets so they don't see 0-history → checkout. ~10-30s.

Ex: warm_session('shopping') → {"warmed":true,"profile":"shopping"}

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

Input Schema

NameRequiredDescriptionDefault
profileNogeneral
max_sitesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 behavioral-disclosure burden and does provide useful context: it says the process uses plausible browsing, takes roughly 10-30 seconds, and shows the returned shape. However, it omits side effects such as cookie/history changes, whether an active browser session is required, and any limits on concurrency or repeated warming.

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 action, profiles, timing, purpose, and an example without unnecessary prose. Every sentence contributes to understanding the 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?

The description is adequate for the core use case and the output schema covers return values, so it need not explain the response fully. Still, the missing 'max_sites' semantics and lack of prerequisite/side-effect information leave meaningful gaps for a session-warming tool with no annotations and 0% schema description coverage.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It meaningfully documents the 'profile' parameter by listing general/shopping/news/minimal and giving an example, but it never explains 'max_sites', leaving one of the two parameters undocumented.

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 ('Pre-warm') and resource ('session') and explains that it performs plausible browsing using one of several profiles. It does not explicitly distinguish this tool from nearby siblings such as check_detection or spawn, so it falls short of a 5.

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?

It clearly states when to use the tool: before bot-detection-heavy targets so they do not see a zero-history session at checkout. It does not name alternatives or exclusions, but the context is strong enough for an agent to know the intended timing.

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