Skip to main content
Glama

tab_close

Close a browser tab by its tab ID, typically obtained from tabs_list or tab_create, to remove it from the Firefox-based browser.

Instructions

Close a tab.

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": {
      "tabId": "<tabId>"
    },
    "name": "tab_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID, from tabs_list or tab_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and discloses almost no behavior: it does not say whether the closed tab's state is lost, whether the active or last remaining tab can be closed, or whether the call requires the tab to exist. For a mutation tool this is a substantial gap.

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

Conciseness3/5

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

The sentence is short and front-loaded with no filler, but its brevity comes from under-specification rather than efficiency; there is no structure conveying effects, constraints, or follow-up.

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

Completeness2/5

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

For a destructive-style mutation with zero annotation coverage and no output schema, the definition should explain consequences and edge cases. As written, an agent has only the bare action and must infer everything about side effects.

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 a single parameter with 100% schema description coverage ("Tab ID, from tabs_list or tab_create"), so the schema already carries the semantics. The description adds no meaning about the identifier, so the baseline 3 applies.

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

Purpose3/5

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

The description names a specific verb and resource ("Close a tab"), but it is effectively a restatement of the tool name tab_close and offers nothing to separate it from siblings like close_cards or tab_create. An agent knows roughly what it does, but gets no scope or differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives for closing other resources (e.g., cards). The only usage hint — where tabId comes from — lives in the schema, not the description.

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