session-broker
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sign_inA | Open a real browser so the user can log into a website. The agent never sees the password. |
| complete_sign_inA | Call after the user says they finished logging in. Saves the session (cookies stay in a local browser profile) and closes the login window. |
| browseA | Read a page using a named session. Omit url to reuse the sign_in url. If the result is LOGIN_REQUIRED, call sign_in, wait, complete_sign_in, retry. |
| list_sessionsA | List saved website sessions and whether a login window is open. |
| revokeA | Delete a named session and its local browser profile. |
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 5 tools
Each tool has a distinct role in the session lifecycle: browsing, listing, deleting, starting login, and completing login. The two-phase sign_in/complete_sign_in flow is clearly separated and not ambiguous.
Most tools follow a clear imperative verb_noun or phrasal-verb pattern like list_sessions, complete_sign_in, and sign_in. Browse and revoke are less descriptive but still readable and not confusing.
Five tools is well-scoped for a session-broker service. Each tool covers a necessary part of the workflow without redundancy.
The tool surface covers the full lifecycle: create a session (sign_in/complete_sign_in), use it (browse), inspect it (list_sessions), and destroy it (revoke). No obvious gaps exist for the stated purpose.