Skip to main content
Glama
Sign In
arc-mcp

arc-mcp

by happylinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_space

Create a new Arc browser space with custom name and icon. Requires Arc restart and disabled sync for changes to persist.

Instructions

Create a new Arc browser space. Requires Arc restart to take effect. Note: Arc sync must be disabled for changes to persist.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new space
iconNoIcon for the space - an emoji (e.g., '🚀') or SF Symbol name (e.g., 'star.fill')star

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes two important behavioral traits: the restart requirement and sync disabling requirement. However, it doesn't mention error conditions, permissions needed, or what happens on failure.

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 sentences, both essential. The first states the core purpose, the second provides critical behavioral constraints. No wasted words, perfectly front-loaded with the main action.

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?

For a creation tool with no annotations and no output schema, the description provides good context about prerequisites and side effects. However, it doesn't describe what happens on success (e.g., returns the created space object) or failure conditions, leaving some gaps.

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 fully documents both parameters. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 ('Create a new Arc browser space') with the exact resource ('space'), distinguishing it from siblings like 'create_workspace' (different resource) or 'add_tab' (different operation). The verb+resource combination is unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Requires Arc restart to take effect' and 'Arc sync must be disabled for changes to persist.' These are crucial prerequisites that tell the agent exactly when this tool is appropriate versus alternatives.

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