Skip to main content
Glama

safe source snapshot

Available Tools

8 tools
hydra_call_toolB

Call a mounted Hydra capability by canonical id, namespaced capability name, or original tool name.

Inputs: tool_name (required), arguments.

hydra_executeB

One-shot autonomous execution: provide a target URL and goal, and Hydra will complete the task automatically.

Inputs: goal (required), target (required).

hydra_inspect_sessionA

Inspect the current mounted Hydra session and route plan.

Inputs: no named parameters.

hydra_memoryC

Inspect or manage H8 web memory for a domain.

Inputs: action (required), domain.

hydra_mountA

Mount a website as a persistent Hydra web capability workspace and return its canonical capability catalog.

Inputs: target (required), goal, credentials.

hydra_probeC

Mount a website for browser-as-probe discovery, then return direct machine-usable capabilities separately from browser-action fallbacks without executing a generated capability.

Inputs: target (required), goal, credentials.

hydra_refreshA

Re-scout the mounted site and refresh its capability catalog.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools have distinct purposes, but 'hydra_mount' and 'hydra_probe' both involve mounting and could cause confusion despite different intents. Overall, agents can distinguish them with careful reading.

    Naming Consistency3/5

    Most tools use the 'hydra_' prefix, but 'navigate' breaks the pattern. The naming styles vary: some are single verbs, some verb_noun, and 'hydra_memory' is a noun. This inconsistency reduces predictability.

    Tool Count5/5

    With 8 tools, the count fits well within the recommended 3-15 range. Each tool appears justified for the server's complex web automation domain.

    Completeness4/5

    The tool set covers mounting, probing, refreshing, inspecting, memory management, calling capabilities, executing tasks, and navigation. A notable gap is the lack of an explicit unmount or close tool, but the core workflow is covered.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides 42+ MCP tools for browser automation, web scraping, and search, enabling AI agents like Claude and Cursor to browse, extract data, and run research agents on the live web.
      8
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that turns any website into an API by capturing or importing API endpoints, enabling AI agents to interact with web services without a browser, with 20-100x token cost reduction versus browser automation.
      132 npm
      132
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Turns any website into a rich set of MCP tools for scraping, crawling, structured data extraction, and automatic API mounting via OpenAPI specs.
      -