Skip to main content
Glama
t3ratech

T3rnel Browser — Session Bridge

Official
by t3ratech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

session_store_login

Idempotent

Encrypt and store domain credentials in the extension's vault so session_login can use them later. Passwords remain secure and are never returned or listed.

Instructions

Encrypt credentials for a domain and store them in the extension's vault, for session_login to use later. Requires the T3rnel Browser extension with Pro. The password is never returned by this or any other tool, and never appears in a listing or an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain the credentials belong to, such as "github.com"
passwordYesPassword to encrypt and store. It is never returned by any tool
usernameYesUsername or email to store
masterPasswordNoPassphrase that unlocks the extension's vault. Never log or persist it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • addedInput schema / properties / domain / description
      Added value: +"Domain the credentials belong to, such as \"github.com\""
    • addedInput schema / properties / masterPassword / description
      Added value: +"Passphrase that unlocks the extension's vault. Never log or persist it"
    • addedInput schema / properties / password / description
      Added value: +"Password to encrypt and store. It is never returned by any tool"
    • addedInput schema / properties / username / description
      Added value: +"Username or email to store"
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate a write (readOnlyHint=false), idempotent, and non-destructive. The description adds the crucial security guarantee that the password is never returned or listed, and the prerequisite of the extension with Pro. This goes beyond what annotations convey.

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

Conciseness5/5

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

Two concise sentences with no filler. The core action is front-loaded, followed by a critical requirement and a security guarantee. Every word contributes value.

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 simple store operation with no output schema, the description covers the purpose, prerequisite, and security behavior. It lacks discussion of error cases or overwrite semantics, but these are less critical given the idempotency hint and simplicity.

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 coverage is 100%, so all four parameters are documented in the schema. The description reinforces the password's privacy but does not add substantive meaning beyond the schema. It meets the baseline but adds little extra.

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 states a specific action (encrypt and store credentials for a domain) and a clear resource (the extension's vault), with an explicit purpose tied to session_login. This distinguishes it from siblings like session_login and session_record_* without ambiguity.

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

Usage Guidelines4/5

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

It clearly indicates when to use: before session_login to persist credentials. It also notes the requirement (extension with Pro) and that the password is never returned. However, it does not explicitly mention 'when not to use' or name alternative tools, though the context of storing vs. logging in is implied.

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