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
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_toolsA

Search 0 tools across 0 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: . Query tip: before searching, distill your intent into key concepts (action verb + target + domain). Pass distilled keywords, not full sentences — the search engine works on token matching, not semantic understanding.

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; you do not need boost_profile just to use a few exact tools. 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 tools added via activate_tools, not base profile tools.

activate_domainB

Activate all tools in a domain at once. Domains: . 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.

Prompts

Interactive templates invoked by user choice

NameDescription
reverse_engineering_assistantSystem prompt and guidelines for using jshookmcp tools effectively.
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.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vmoranv/jshookmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server