NodeLane Act
Server 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| site.contextA | List browser targets with opaque targetIds. With a site or supported URL, automatically open a tab if missing; set openIfMissing=false for a pure lookup. Never replaces existing tabs. Returns no page bodies or credentials. |
| site.discoverA | Discover installed sites or relevant operations. site alone returns a compact catalog; site+query returns matching schemas; site+operation returns one exact schema. No unrelated website schemas are returned. |
| site.executeB | Execute a discovered operation on a targetId using its exact args schema. User-authorized writes execute directly in the browser. Pass returned pagination args for the next website page. For cached oversized output pass only resultId, offset and maxChars, which never repeats an operation. |
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 3 tools
Each tool serves a distinct phase: site.context manages browser targets, site.discover retrieves operation schemas, and site.execute performs operations. The descriptions clearly delineate their roles, leaving little room for confusion.
All tools use a consistent 'site.' prefix and lowercase dot notation, but site.context is a noun while the others are verbs, a minor deviation from a uniform verb-based pattern.
Three tools are well-scoped for a meta-execution model: one to establish context, one to discover available operations, and one to execute them. This minimal surface avoids redundancy and each tool earns its place.
The set covers the core workflow of target selection, schema discovery, and execution, but lacks explicit tools for tab management (e.g., closing tabs) or direct page state inspection, which are minor gaps agents might work around via discovered operations.