Skip to main content
Glama
Sign In
arc-mcp

arc-mcp

by happylinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

focus_space

Switch to a specific Arc browser space using AppleScript to organize and manage browsing sessions programmatically.

Instructions

Switch to a specific Arc browser space (uses AppleScript)

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": {
      "space": "<space>"
    },
    "name": "focus_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceYesName or ID of the space to focus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions AppleScript implementation but doesn't describe what happens during the switch (e.g., does it close current space, require specific permissions, have side effects on tabs, or show error messages for invalid spaces).

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and includes only essential technical context about AppleScript.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after switching (success indicators, error conditions, or return values), leaving significant gaps for agent understanding.

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 description coverage is 100%, so the schema already documents the 'space' parameter fully. The description doesn't add any additional meaning about parameter usage beyond what the schema provides, maintaining the baseline score.

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 clearly states the specific action ('Switch to') and resource ('Arc browser space'), distinguishing it from siblings like 'create_space' or 'list_spaces'. It explicitly mentions the implementation method ('uses AppleScript'), which adds technical context.

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?

The description implies usage when needing to change the active space in Arc browser, but doesn't explicitly state when to use this vs. alternatives like 'create_space' or 'list_spaces'. No guidance on prerequisites or exclusions is provided.

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