Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JSHOOK_BASE_PROFILENoBase profile for tool discovery tiers: search, workflow, or fullsearch

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {}
}
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}
extensions
{
  "io.modelcontextprotocol/skills": {
    "directoryRead": true
  }
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_toolsA

Search 736 tools across 36 capability domains. This includes built-in tools plus any loaded plugin/workflow tools (0 currently loaded). In search-tier sessions, call this before assuming a capability is unavailable. Use activate_tools for exact matches, activate_domain for an entire domain. Domains: browser (85) | memory (75) | native-emulator (57) | binary-instrument (46) | network (38) | process (29) | tls-inspector (29) | adb-bridge (26) | core (25) | debugger (21) | exploit-dev (21) | v8-inspector (21) | protocol-analysis (20) | platform (18) | maintenance (17) | streaming (17) | wasm (17) | dart-inspector (16) | syscall-hook (15) | instrumentation (13) | workflow (13) | coordination (12) | canvas (11) | proxy (11) | trace (10) | webgpu (10) | cross-domain (8) | mojo-ipc (8) | transform (8) | extension-registry (7) | graphql (7) | sourcemap (7) | native-bridge (6) | encoding (5) | tasks (4) | session (3). Query tip: before searching, distill your intent into key concepts (action verb + target + domain). The engine combines token matching, fuzzy names, profile context, and optional static embeddings.

route_toolA

One-stop tool router: accepts a natural language task description, returns recommended tools and next actions. Automatically detects workflow patterns, recommends activation order, and provides example arguments. Use this instead of search_tools when you want guided tool discovery with actionable next steps.

describe_toolA

Get detailed information about a specific tool, including its input schema. Use this to see the exact parameters a tool expects before calling it.

activate_toolsA

Dynamically register specific tools by name, regardless of current base tier. Use after search_tools to enable exactly the tools you need. In search-tier sessions this is usually enough; use activate_domain when you need every tool in a domain. Activated tools appear in the tool list immediately. If tools do not appear after activation, use call_tool to invoke them directly.

deactivate_toolsA

Remove previously activated tools to free context. Only affects dynamically activated tools (added via activate_tools, activate_domain, or extension activation), not base profile tools.

activate_domainA

Register every tool in a single domain at once. Use this when a task needs a whole capability area; prefer search_tools or activate_tools when you only need a few specific tools, because activating a domain costs far more context. Domains: . Activated tools appear in the tool list immediately; if your client does not refresh its tool list, invoke them with call_tool. Activation draws on the session context budget: when the budget is full, least-recently-used tools are evicted to make room, and the response reports what was activated and what was evicted. Pass precheck: true to preview wouldActivate / wouldEvict without changing anything. Activated tools auto-deactivate after ttlMinutes (default 30; pass 0 for no expiry). Use reload_extensions first to include external plugin/workflow domains.

call_toolA

Execute an already-active tool by name. Use this when activate_tools/activate_domain registered a tool but your client did not refresh its tool list. Does not auto-activate inactive tools.

coverage_reportA

Report which tools have been called in the current runtime and which known tools remain uncalled. Loads all domains first so the uncalled list reflects the full tool catalog, not just currently active tools.

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_anti_debugRunbook and scripts for defeating debugger protections and traps.
hook_generation_guideInstructions on how to deploy and use hooks generated by the hook builder.

Resources

Contextual data attached and managed by the client

NameDescription
evidence_graph_jsonSerializable snapshot of the current reverse evidence graph.
evidence_graph_markdownMarkdown report for the current reverse evidence graph.
instrumentation_sessionsExpanded snapshots for all active instrumentation sessions.
search_engine_statusCurrent status of the multi-signal tool search engine.
token_budget_statsCurrent token budget usage, top-10 tool distribution, and optimization suggestions.
activation_stateCurrently activated tools, per-domain TTL remaining, and auto-pruner predictions.
tool_coverageCalled vs uncalled tools in the current runtime, with last-call metadata.
cache_statsGlobal cache entry count, total size, and per-cache-instance hit rates.
browser_tabsList of currently open browser tabs with URL, title, and tabIndex.
Domain: adb-bridge0 tools
Domain: core0 tools
Domain: binary-instrument0 tools
Domain: browser0 tools
Domain: canvas0 tools
Domain: coordination0 tools
Domain: cross-domain0 tools
Domain: dart-inspector0 tools
Domain: debugger0 tools
Domain: encoding0 tools
Domain: exploit-dev0 tools
Domain: extension-registry0 tools
Domain: graphql0 tools
Domain: instrumentation0 tools
Domain: maintenance0 tools
Domain: memory0 tools
Domain: mojo-ipc0 tools
Domain: native-bridge0 tools
Domain: native-emulator0 tools
Domain: network0 tools
Domain: platform0 tools
Domain: process0 tools
Domain: protocol-analysis0 tools
Domain: proxy0 tools
Domain: session0 tools
Domain: sourcemap0 tools
Domain: streaming0 tools
Domain: syscall-hook0 tools
Domain: tasks0 tools
Domain: tls-inspector0 tools
Domain: trace0 tools
Domain: transform0 tools
Domain: v8-inspector0 tools
Domain: wasm0 tools
Domain: webgpu0 tools
Domain: workflow0 tools
best-practices配置与日常使用的最佳实践:避免常见坑、性能与安全建议
configuration配置参考:环境变量、profile、阈值等全部配置项说明
getting-started快速开始:五分钟接入 jshookmcp——安装、MCP 客户端配置与首次调用
telemetry遥测与可观测性:默认开启的指标、OTLP 导出、search.query span 与 /health
tool-selection工具路由与生命周期:36 域命名空间、按需激活、profile 分层下如何选择与调度 jshookmcp 工具
troubleshootingTroubleshooting:安装、连接、工具调用失败的诊断步骤与修复方法

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have clearly distinct roles: discovery (search_tools, route_tool, describe_tool), activation lifecycle (activate_tools, activate_domain, deactivate_tools), execution (call_tool), and reporting (coverage_report). The only mild overlaps are search_tools vs route_tool (both discovery) and activate_tools vs activate_domain, but the descriptions explicitly differentiate them by intent and cost.

Naming Consistency4/5

Nearly all names follow a consistent verb_noun snake_case pattern (search_tools, activate_tools, call_tool, describe_tool). The main deviation is coverage_report, which is a noun phrase rather than an action, but it remains readable and predictable.

Tool Count5/5

Eight tools is well-scoped for a meta-server that manages 736 tools across 36 domains. Each tool covers a distinct phase of the discovery-activation-execution lifecycle and none feels redundant or filler.

Completeness3/5

The surface covers discovery, activation, deactivation, execution, and coverage reporting, but there is no dedicated tool to list currently active tools or enumerate domains, and activate_domain's domain list is empty. The descriptions also reference reload_extensions, which is not present in the tool set, creating a dead end for plugin/workflow domain loading.

Maintenance

ActivityActive
ResponsivenessOutdated data