Skip to main content
Glama
t3ratech

T3rnel Browser — Session Bridge

Official
by t3ratech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

session_login

Idempotent

Decrypt saved credentials for a domain and populate the page's sign-in form. Uses the extension vault to complete login without manual or scripted authentication.

Instructions

Decrypt stored credentials for a domain and fill them into the page's sign-in form. Requires the T3rnel Browser extension with Pro, because the encrypted vault lives in the extension; the refusal comes from the extension rather than from this bridge, so there is one gate rather than two that can disagree. The standalone browser has no vault — sign in once by hand in its profile instead, and the session persists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab holding the sign-in form; uses the active tab when omitted
domainYesDomain the credentials are saved for, such as "github.com"
submitNoIgnored; kept so older callers do not break
masterPasswordNoPassphrase that unlocks the extension's vault. Never log or persist it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • changedInput schema / properties / domain / description
      Previous value: -"Domain the credentials are saved for, e.g. \"github.com\""New value: +"Domain the credentials are saved for, such as \"github.com\""
    • addedInput schema / properties / domain / examples
      Added value: +[
+  "github.com"
+]
    • addedInput schema / properties / masterPassword / description
      Added value: +"Passphrase that unlocks the extension's vault. Never log or persist it"
    • changedInput schema / properties / submit / description
      Previous value: -"Ignored; kept for compatibility"New value: +"Ignored; kept so older callers do not break"
    • addedInput schema / properties / tabId / description
      Added value: +"Tab holding the sign-in form; uses the active tab when omitted"
  2. First observedv1.1.1

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate this is not read-only and not destructive. The description adds useful behavioral context by explaining where the vault lives, that refusal comes from the extension rather than the bridge, and that a standalone browser profile cannot use this tool. This goes beyond what annotations alone convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary behavior, then provides prerequisite and fallback guidance. It is reasonably concise, though the 'one gate rather than two that can disagree' phrasing is slightly elaborate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with full schema coverage and safety annotations, the description covers the main operational context: prerequisites, error source, and fallback behavior. It does not describe return values, but there is no output schema to explain, and the core calling conditions are clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents each parameter. The description reinforces the domain and fill behavior but does not add new parameter-level semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: it decrypts stored credentials for a domain and fills them into the sign-in form. This clearly distinguishes it from manual form-filling siblings like session_fill and from credential-saving siblings like session_store_login.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when the tool works (T3rnel Browser extension with Pro) and when it does not (standalone browser has no vault), including the alternative action: sign in once by hand. This gives an agent concrete decision rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools