Skip to main content
Glama
Sign In
Seleniumboot MCP

Seleniumboot MCP

by seleniumboot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

detect_selenium_boot

Check whether the working directory is a Selenium Boot project before generating Java code; if detected, use framework='selenium_boot' for correct output.

Instructions

Detect whether the working directory is a Selenium Boot project. Call BEFORE generating Java; if detected=true use framework='selenium_boot'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "detect_selenium_boot"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_dirNoOptional path to start detection from. Defaults to the server's working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.9

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Detect' implies a non-mutating inspection and the result field (detected=true) is revealed, but it doesn't say what markers it inspects, what happens on failure, or whether a false result is authoritative.

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?

Two compact sentences with zero waste: the detection claim first, then the timing and branch guidance. Nothing to trim.

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

Completeness4/5

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

For a single-optional-parameter read-only check with no output schema, the description covers what it does, when to call it, and how to act on the result. Only the detection mechanism and negative-result handling are left implicit.

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 coverage is 100% and the project_dir parameter is fully documented in the schema, including its default. The description adds only the working-directory framing already implied, so baseline 3 applies.

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?

States a specific verb and resource: detects whether the working directory is a Selenium Boot project. It distinguishes itself from generation-oriented siblings by tying itself to pre-generation checks, though it doesn't explicitly name the sibling ('generate') it precedes.

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

Usage Guidelines4/5

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

Gives explicit ordering guidance ('Call BEFORE generating Java') and a concrete follow-up action conditioned on the result (use framework='selenium_boot'). No explicit when-not-to-call case is given, but the trigger condition is clear.

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