Skip to main content
Glama

safari_search_tabs

Search for text across all open Safari tabs to quickly locate information without manually switching between tabs.

Instructions

Search text across Safari tabs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition entry in the TOOLS array listing 'safari_search_tabs' with its description.
    ["safari_search_tabs", "Search text across Safari tabs"],
  • server.js:106-109 (registration)
    Registration loop that registers 'safari_search_tabs' (and all other tools) on the MCP server with a stub handler.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
Behavior2/5

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

The description only mentions 'search', implying a read-only operation, but does not disclose any behavioral traits such as whether it returns a list, modifies tabs, or requires permissions. Since no annotations are provided, the description fails to compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (4 words), which is efficient but at the cost of completeness. It is front-loaded with the key action, but lacks detail that would help the agent.

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?

Given that there is no output schema, no annotations, and many sibling tools, the description is insufficient. It does not explain what the tool returns, how it behaves, or how it relates to other Safari tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so the description does not need to add parameter meaning. Baseline for 0 parameters is 4, and the description does not provide any misleading or contradictory info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'search' and the resource 'Safari tabs', which distinguishes it from sibling tools like safari_read_tab (which reads a specific tab) and list_safari_bookmarks. However, it could be more specific about whether it searches titles, content, or both.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like safari_read_tab or list_safari_bookmarks. The description does not set any context for its use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server