arc_tabsList visible Arc browser tabs with their IDs, titles, and URLs. Distinguishes tabs opened by this server from user's own tabs to guide safe interaction.
Lista as abas do Arc visíveis, com id, título e URL. owned: true são as abas que este servidor abriu; owned: false são abas do próprio usuário — só atue nelas se ele pedir, passando o tabId explicitamente.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explains the ownership distinction (server-opened vs. user tabs) and implies a read-only behavior. With no annotations, this transparency is valuable for safe invocation.
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?
The description is concise, using a single sentence and a short clarifying note. There is no redundancy or unnecessary detail.
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 simple no-parameter listing tool, the description fully covers functionality and the important ownership nuance. Nothing essential is missing for correct invocation.
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?
The tool has zero parameters, so schema coverage is tautologically high. The description adds no parameter-specific details because none exist, matching the baseline expectation.
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 lists visible Arc tabs with id, title, and URL, and further distinguishes owned vs. user tabs. This is specific and unambiguous.
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?
It provides a practical usage guideline: acting on user-owned tabs only when explicitly asked and passing tabId. Although it does not name alternative tools, the condition for appropriate use is explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.