arc_new_little_arc
Open a URL in a dedicated Little Arc window for focused browsing without tab clutter.
Instructions
Little Arc ウィンドウで URL を開く
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 開く URL |
Open a URL in a dedicated Little Arc window for focused browsing without tab clutter.
Little Arc ウィンドウで URL を開く
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 開く URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It indicates a new Little Arc window is opened, but lacks details on whether an existing window is reused, if the window closes automatically, or any side effects. Basic but not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, no wasted words. Perfectly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description is adequate but could mention that a new Little Arc window is created. No major gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter description matches the schema. The description adds no extra meaning beyond the parameter name and type.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool opens a URL in a 'Little Arc' window, which is a specific type of window in Arc browser. This distinguishes it from generic open URL or new window tools, though it does not explicitly contrast with siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like arc_open_url or arc_new_window. The description does not mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yzanbo/arc-browser-control-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server