safari_new_tab
Open a new tab in Safari, optionally navigating to a specified URL.
Instructions
Open a new tab, optionally with a URL
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | URL to open (empty for blank tab) |
Open a new tab in Safari, optionally navigating to a specified URL.
Open a new tab, optionally with a URL
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | URL to open (empty for blank tab) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose behavioral traits such as whether the new tab is activated, if it returns a tab ID, or any side effects. Minimal information beyond the core action.
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?
Single sentence, 9 words, front-loaded with the verb and resource. Efficient and to the point.
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?
No output schema, and description does not clarify what happens after opening (e.g., tab focus, return value). Given sibling tools like switch_tab and close_tab, more context is needed for completeness.
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% with one optional parameter. Description adds no extra meaning beyond the schema's description. Baseline score of 3 is appropriate.
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?
Description clearly states verb 'open' and resource 'new tab', with optional URL. Differentiates from siblings like close_tab, switch_tab, and navigate. No tautology.
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 navigate (which also opens a page) or switch_tab. Lacks context for optimal use.
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/achiya-automation/safari-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server