Skip to main content
Glama
WhiteNightShadow

frx-director-mcp

by WhiteNightShadow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List the browser-side tools

agent_tools

Lists available browser-side reverse-engineering tools with parameters and confirmation flags; filter by prefix or keyword and return compact metadata. Read-only, no side effects.

Instructions

列出浏览器侧实际可用的工具清单(名称/说明/是否需确认/参数名)。支持 prefix/query 筛选和 compact 精简返回，工具数量以当前浏览器为准。包含引擎级逆向工具(signer_trace/jsvmp_trace/closure_read/webapi_trace/whitebox_diff/wasm_probe 等)、环境管理以及 Firefox 扩展查询/管理(addons_query/addons_manage)。all 分组可委派 worker 或用 agent_call_tool 直调。只读、无副作用。

Input Schema

NameRequiredDescriptionDefault
limitNo返回数量上限；默认全量
queryNo名称/说明中的关键词，不是正则
prefixNo工具名前缀，如 page_ 或 net_
compactNo只返回名称、参数名和确认标志；默认 false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "只返回名称、参数名和确认标志；默认 false",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "返回数量上限；默认全量",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / prefix
      Added value: +{
+  "description": "工具名前缀，如 page_ 或 net_",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "名称/说明中的关键词，不是正则",
+  "maxLength": 160,
+  "type": "string"
+}
  2. Addedv0.3.0

TDQS

A4.1/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 declares '只读、无副作用' and warns the tool count is dynamic ('工具数量以当前浏览器为准'), which is an important behavioral trait. It does not discuss pagination versus the limit param or error behavior, so it is not exhaustive.

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?

Purpose and scope are front-loaded, and the tool-family enumeration adds useful signal rather than filler. The list of engine-level tool names is mildly long but parenthetical and earns its place by telling the agent what to expect.

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

Completeness4/5

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

No output schema exists, but the description explains the returned shape (name/description/confirmation flag/param names) and the compact mode, so an agent knows what comes back. With 4 fully documented optional params and no annotations, the definition is nearly self-sufficient.

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 already documents all four parameters with semantics. The description only restates prefix/query filtering and compact behavior at a high level, adding little beyond the schema — baseline 3.

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 and resource ('列出浏览器侧实际可用的工具清单') plus the exact fields returned (名称/说明/是否需确认/参数名). It clearly distinguishes itself from the sibling agent_call_tool by framing this as discovery versus direct invocation, so an agent can pick between them without opening the schemas.

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 clear context: it enumerates what categories are covered (engine RE tools, env management, Firefox addons) and notes the 'all' group can delegate to a worker or use agent_call_tool directly. It lacks an explicit when-not-to-use statement, hence not a 5.

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