Skip to main content
Glama
WhiteNightShadow

frx-director-mcp

by WhiteNightShadow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a Firefox Reverse environment

frx_env_create

Creates a Firefox environment with configurable locale, language, timezone, and consistency mode; native-consistent mode preserves real Screen/DPR/GPU values, legacy uses browser defaults.

Instructions

一键新建 Firefox 环境；新版内核默认原生一致策略，保持真实 Screen/DPR/GPU，默认中国大陆简体中文。旧版浏览器仍按自身默认策略执行。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo环境名称
localeNo地区标识，如 zh-CN
languageNo首选语言，如 zh-CN
timezoneNo时区，如 Asia/Shanghai
languagesNo语言列表，如 [zh-CN, zh, en-US, en]
randomizeNo历史策略可随机分辨率、DPR 和 CPU；原生一致策略不随机硬件值
consistencyModeNo需支持原生一致策略的新版 Firefox Reverse；不传使用浏览器默认策略

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.8
    • addedInput schema / properties / consistencyMode
      Added value: +{
+  "description": "需支持原生一致策略的新版 Firefox Reverse；不传使用浏览器默认策略",
+  "enum": [
+    "native-consistent",
+    "legacy"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / randomize / description
      Previous value: -"默认 true，只随机分辨率、DPR 和 CPU 核数等非身份参数"New value: +"历史策略可随机分辨率、DPR 和 CPU；原生一致策略不随机硬件值"
  2. Changed6 schema fields changedv0.3.4
    • removedInput schema / properties / browser
      Removed value: -{
-  "description": "默认 chromium；也可传 firefox",
-  "type": "string"
-}
    • addedInput schema / properties / language
      Added value: +{
+  "description": "首选语言，如 zh-CN",
+  "type": "string"
+}
    • addedInput schema / properties / languages
      Added value: +{
+  "description": "语言列表，如 [zh-CN, zh, en-US, en]",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "地区标识，如 zh-CN",
+  "type": "string"
+}
    • changedInput schema / properties / randomize / description
      Previous value: -"默认 true，随机生成一致的桌面参数"New value: +"默认 true，只随机分辨率、DPR 和 CPU 核数等非身份参数"
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "时区，如 Asia/Shanghai",
+  "type": "string"
+}
  3. Addedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well. It discloses default locale behavior (zh-CN), native consistency handling of hardware values, and the distinction between new and old browser defaults. This is valuable context beyond the schema.

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 short and efficient, with key defaults and behavior front-loaded. No wasted words, and it covers the most important behavioral quirks. Could be slightly more structured but is appropriately concise.

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?

For a create tool with 7 optional parameters and no output schema, the description covers defaults and consistency modes but doesn't explain potential side effects, validation failures, or required parameters (since none are required, it's clear an empty call is possible). It lacks guidance on naming conventions and error handling, but is reasonably complete for a creation operation.

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 100%, so the schema documents all parameters. The description adds context on consistencyMode and randomize, but doesn't elaborate on how locale, language, or timezone interact. It adds some clarity but doesn't go beyond the schema's per-parameter descriptions.

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 action (create) and resource (Firefox Reverse environment), and mentions new versions default to native consistency with real Screen/DPR/GPU and mainland China locale. It distinguishes from siblings like frx_env_open and frx_env_delete, but could be more precise about what 'environment' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like frx_env_import_json or frx_env_rename. The description implies it's for creating new environments from scratch, but doesn't state exclusions or alternatives. A user might wonder if this is preferred over import for fresh setups.

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