Skip to main content
Glama

Related Servers

Alternatives to nokk

Related Servers

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation4/5

The reading tools (snapshot, read_text, read_html) overlap in that all return page content, but the descriptions clearly carve out distinct roles — numbered interactive outline vs visible text vs raw HTML — and explicitly recommend snapshot over read_html. challenge_state and solve_challenge are cleanly split into report vs act, and evaluate is explicitly framed as a fallback for 'data the other tools do not read'.

Naming Consistency3/5

All names are snake_case, which avoids casing chaos, but conventions are mixed: action verbs (open, click, fill, evaluate, reset, solve_challenge) sit alongside bare nouns (snapshot, links, challenge_state). Readable and semi-predictable (nouns for getters, verbs for actions), but not a uniform verb_noun pattern.

Tool Count5/5

Eleven tools is well within the sweet spot for a browser automation server, and each has a clear, non-redundant role in the open → snapshot → act → read lifecycle. Nothing feels padded or missing at the count level.

Completeness4/5

Core lifecycle (open, solve challenge, inspect, click/fill, reset) is fully covered, but common browser operations like back/forward navigation, key presses, select/hover, and downloads lack dedicated tools. The evaluate escape hatch lets agents work around most of these gaps, so they are minor rather than blocking.

Maintenance

ActivityActive
ResponsivenessLimited data