Skip to main content
Glama

Read a browser session

get_browser
Read-onlyIdempotent

Reads a browser session: running or ended, why it ended, its seconds, steps, bytes and charge so far. No charge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe browser session's id, as the opened browser returned it.

Output Schema

NameRequiredDescriptionDefault
idNo
bytesNo
priceNo
limitsNo
statusNo
actionsNo
secondsNo
ended_atNo
headlessNo
live_urlNo
metadataNo
viewportNo
timeout_sNo
created_atNo
expires_atNo
keep_aliveNo
started_atNo
actions_urlNo
block_mediaNo
charged_usdNo
connect_urlNo
ended_reasonNo
idle_timeout_sNo
allowed_domainsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "actions": {
      +      "type": "integer"
      +    },
      +    "actions_url": {
      +      "type": "string"
      +    },
      +    "allowed_domains": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "block_media": {
      +      "type": "boolean"
      +    },
      +    "bytes": {
      +      "type": "integer"
      +    },
      +    "charged_usd": {
      +      "type": "number"
      +    },
      +    "connect_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "created_at": {
      +      "type": "string"
      +    },
      +    "ended_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "ended_reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "headless": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "idle_timeout_s": {
      +      "type": "integer"
      +    },
      +    "keep_alive": {
      +      "type": "boolean"
      +    },
      +    "limits": {
      +      "type": "object"
      +    },
      +    "live_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "metadata": {
      +      "type": "object"
      +    },
      +    "price": {
      +      "type": "object"
      +    },
      +    "seconds": {
      +      "type": "integer"
      +    },
      +    "started_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "timeout_s": {
      +      "type": "integer"
      +    },
      +    "viewport": {
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / session_id / description
      Added value: +"The browser session's id, as the opened browser returned it."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description only needs to add context, and it does: it enumerates the reported state fields and states 'No charge,' a behavioral property (calling it costs nothing) not encoded in the annotations. It says nothing about error behavior for an unknown or expired session_id.

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 short sentences, front-loaded with the action and the returned values, with the 'No charge' caveat placed last where it reads as a qualifier. No wasted words.

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?

Given an output schema that defines the return shape, rich annotations, and a single fully documented parameter, the description covers what the tool reads and the no-cost property. The remaining gap is routing guidance relative to the many browser_* siblings.

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?

There is one parameter at 100% schema coverage, and the schema already explains that session_id is the id as returned by the opened browser. The description adds no further detail about the parameter, so the baseline of 3 applies.

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

Purpose4/5

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

A specific verb plus resource ('Reads a browser session') followed by the exact information returned: running/ended state, termination reason, seconds, steps, bytes, and charge. An agent can distinguish this session-level read from the page-level browser_* action siblings, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: needing a session's status, duration, or accrued charge tells you when to call it. There is no statement of when not to use it or which sibling tool covers adjacent needs such as page content or navigation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.