Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Close a tab

tab_close

Closes a specified browser tab in Chromaphore by tab identifier, helping AI agents manage open tabs and reduce clutter.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
tabYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing. It does not say whether unsaved state is discarded, what happens when the last tab is closed, whether closing the active tab shifts focus, or whether an unknown tab yields an error.

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

Conciseness2/5

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

Two words are not concise so much as under-specified; there is no wasted text, but the sentence earns its place only by naming the operation and provides no structure an agent can act on.

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

Completeness1/5

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

With no annotations, no output schema, and an undocumented required parameter, the definition is far too thin for a mutation tool that destroys a browsing context. It omits both the parameter contract and the side effects an agent needs before calling it.

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

Parameters1/5

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

Schema description coverage is 0% and the single required parameter "tab" is an untyped string. The description does not clarify whether it accepts a tab ID, index, URL, or title, so the caller must guess the expected format.

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

Purpose2/5

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

"Closes a tab" restates the tool name and title without adding anything: no scope, no indication of which tab instance is affected, and no differentiation from sibling tools such as browser_close or tab_select.

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 guidance on when to use this instead of browser_close, nor any precondition such as whether the tab must be selected or whether the input must be an existing tab handle. The only implied usage comes from the name itself.

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