pilotfish
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_navigateA | Open an http(s) URL in the current tab. Returns evidence and a snapshot of the visible screen (elements carry refs like e12), with counts of what is above and below. Words like cheapest, latest, highest-rated or most mean the site's own sort or tab for that order (a list's default order is usually something else, e.g. 'Best' or 'Featured'): apply it, then read the top. Over several sites, finish one and note the values the next needs before opening it. A task that names no site: search the web first with your own search tool to pick the site, or answer from the search when that is enough; open a site when the task needs one (a price for dates, a form, an account). |
| browser_snapshotA | The current page as a compact tree of headings, text and elements with refs (e12) to act on: three screens around the viewport, or everything with whole_page. Refs stay valid while their element is on the page. |
| browser_clickA | Click an element by ref. Refuses with a reason (obscured, stale, not visible) instead of clicking the wrong thing. Returns evidence of what changed. |
| browser_typeA | Replace the text of an input, textarea or editable element by ref (never appends). In an autocomplete box the result shows its suggestions: browser_click one. For a , browser_select. Returns what changed. |
| browser_selectA | Choose options of a native by label or value, replacing the current selection (unlisted options are unselected). Custom dropdown: browser_click it, then the option. Returns the values selected and what changed. |
| browser_pressA | Press a key or shortcut on whatever has focus (no ref; browser_click a field first). E.g. Escape closes a dialog, ArrowDown then Enter picks a suggestion; Enter may submit a form; reload keys are refused. For text, browser_type. Returns what changed. |
| browser_scrollA | Scroll the page about one screen; returns the screen now in view, with refs. To reach a named element, browser_find; for text, browser_get_text. |
| browser_screenshotA | JPEG of the current viewport. Prefer browser_snapshot (cheaper, has refs); use this when layout or images matter. |
| browser_get_textA | Readable text of the page (PDFs too), secrets masked, without refs. To read a few values or a list, browser_query is far smaller. |
| browser_queryA | Read just the values you need (prices, counts, titles, a results list) with a read-only JavaScript expression returning JSON (at most 4000 characters): the cheapest way to read, far smaller than browser_get_text or a snapshot. It runs in a world of its own where clicks, typing, submits and network writes are refused. |
| browser_findA | Refs of elements anywhere on the page, outside the visible screen too, by the words they show or are labelled with, best match first. Separate several targets by commas. |
| browser_actionsA | Several steps in order in one call, e.g. fill a form's fields and submit it; each gets the same checks as its own tool. Stops at the first that fails, or after one that moves the page to another address (later refs would belong to the old page). Returns a line per step and the evidence and visible screen after the last one run. |
| browser_resumeA | When a result says NEEDS A PERSON (a sign-in, a one-time code or 2FA, a device approval, a CAPTCHA), tell the user in your reply what the page needs and that the pilotfish browser window is open on it; when they have done it there (or right after asking), call this and carry on: it waits until the page has moved on, then returns it. BLOCKED and STOP mean the site cannot be continued that way. |
| browser_waitA | Wait 0.5-10 seconds (until/gone: up to that, returning once the text appears or goes), then return what changed. Only for a page still loading or saying it is working: actions already wait for the requests they start. |
| browser_tabsA | List the open tabs (the current one is marked). switch_to makes another tab current and returns its snapshot. |
| browser_closeA | Only to start over: closes the browser, and the next call starts a fresh one (cookies and logins are gone). It closes by itself when the client disconnects. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools have sharply distinct purposes, and the descriptions actively route the agent (snapshot vs screenshot vs get_text vs query, click vs type vs select vs press). The reading cluster (snapshot, find, get_text, query) overlaps somewhat in that all reveal page content, but each is clearly scoped by cost and by whether refs are returned. No two tools appear to do the same thing.
Every name carries the same browser_ prefix and is lowercase snake_case, which makes the set predictable. A few names are bare nouns (browser_snapshot, browser_screenshot, browser_tabs, browser_actions) rather than verb_noun like browser_get_text, so it is not a single uniform pattern. Still highly consistent overall.
Sixteen tools is on the heavy side but sits just inside a reasonable range for a full browser-automation surface. Each tool maps to a real capability (navigate, read, click, type, select, press, scroll, wait, tabs, close, batch, human handoff) rather than being filler. The count is defensible, though a few read variants could conceivably be merged.
The core browser lifecycle and interaction loop is fully covered, including batch actions and a NEEDS A PERSON handoff via browser_resume, which is a thoughtful completeness feature. Gaps are minor: no explicit hover or drag, no back/forward history navigation, and no file-upload tool. Agents can usually work around these (e.g. keyboard shortcuts), but not always.