Skip to main content
Glama
Sign In
mcp-chrome-server

mcp-chrome-server

by dlwjdtn535
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tool_switch_to_frame

Switch browser focus to a specific iframe or frame by providing its reference, enabling interaction with elements inside that frame.

Instructions

Switch to a specific frame.

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

Input Schema

NameRequiredDescriptionDefault
frame_referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits, such as what happens to the current context, whether the frame is identified by index or name, or any side effects.

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 a single short sentence, which is concise but may be too minimal. It lacks structure and does not provide enough information for an agent to use it effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one required parameter, no output schema, and no annotations, the description is severely incomplete. It fails to explain the tool's purpose in the context of browser automation or how it interacts with other tools.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to the 'frame_reference' parameter. It does not explain what values are acceptable (e.g., frame name, id, index) or how they are used.

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 states the tool's action (switch to a frame) and resource (frame), which is clear. However, it does not specify the type of frame (e.g., iframe) or differentiate from switching to default content or windows, which could be improved.

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?

The description provides no guidance on when to use this tool versus alternatives like switch_to_window or switch_to_default_content. An agent would need to infer usage from context.

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