Skip to main content
Glama

open_site

Opens a page on infinitebacklog.net in a visible browser window, prompting for a browser if none is selected so you can sign in once and reuse the session.

Instructions

Open a page on infinitebacklog.net in this server's browser window.

Asks which browser to use first if none was chosen. The window is visible by default (Infinite Backlog renders blank in headless mode). Sign in once there; later calls reuse it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo/
wait_msNo
headlessNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / headless / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / headless / default
      Previous value: -trueNew value: +null
    • removedInput schema / properties / headless / type
      Removed value: -"boolean"
  2. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: an interactive browser-selection prompt, a visible window by default, headless mode rendering blank, and session reuse after signing in. It omits what happens on failure, whether navigation is blocking, and how the wait behaves, so it's solid but incomplete for a browser-control tool.

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?

Three short lines, front-loaded with the core action and followed by the operational caveats an agent needs. No filler, though the parenthetical about headless rendering is slightly awkwardly placed.

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?

An output schema exists, so return values needn't be described, and the description covers the key operational facts (browser selection, visible window, sign-in persistence). The remaining gap is the unexplained path and wait_ms semantics.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate. It only implicitly explains 'headless' via the note that the site renders blank in headless mode; 'path' (default '/') and 'wait_ms' (default 2000) get no explanation of format, units, or effect.

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?

States a specific verb and target ('Open a page on infinitebacklog.net in this server's browser window'), which is enough to separate it from siblings like choose_browser, close_browser, and login. It doesn't explicitly name those siblings, so it stops short of a 5.

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?

Implied usage is clear from the context (browse the site, sign in once, later calls reuse the session), and the note about being asked which browser to use flags a prerequisite. However, there is no explicit statement of when to use this versus choose_browser, login, or current_url.

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