Skip to main content
Glama
Sign In
kiro-frontend-engineer-mcp

kiro-frontend-engineer-mcp

by Josephjyinn516
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run_kane_cli

Opens a target URL in a headless browser and performs interaction sequences to visually validate rendered components.

Instructions

Orchestrate a real browser run via kane-cli. Accepts a target URL and optional interaction sequences (click, type, scroll) to visually validate rendered components.

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": {
      "url": "<url>"
    },
    "name": "run_kane_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL to open in headless browser
interactionsNoOrdered list of browser interactions to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description provides some behavioral context: 'real browser run' and 'visually validate rendered components'. However, it omits side effects, required permissions, or error scenarios, leaving gaps despite lacking annotation support.

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

Conciseness5/5

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

A single, well-structured sentence immediately conveys the tool's purpose and key inputs. No unnecessary words or repetition.

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

Completeness3/5

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

For a tool with two well-documented parameters and no output schema, the description adequately explains what the tool does. However, it lacks information about return values or result format, which is expected given the absence of an output schema.

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

Parameters3/5

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

Schema description coverage is 100% for both parameters. The description mentions 'optional interaction sequences (click, type, scroll)' which aligns with the schema but adds no extra meaning beyond the schema's own descriptions.

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?

Description clearly states the tool orchestrates a real browser run via kane-cli, accepts URL and optional interactions for visual validation. This distinguishes from siblings like github tools but not from execute_playwright_test, which is a similar browser testing tool.

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 explicit guidance on when to use this tool versus alternatives such as 'execute_playwright_test'. The description lacks context for selection criteria or prerequisites.

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