Skip to main content
Glama
Sign In
Seleniumboot MCP

Seleniumboot MCP

by seleniumboot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

assert_url

Verify the current browser URL equals or contains the expected value to confirm navigation or page state.

Instructions

Assert the current URL equals or contains expected value.

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": {
      "expected": "<expected>"
    },
    "name": "assert_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
exactNo
expectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.7

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, but it only states the matching behavior and not what happens on assertion failure, whether it returns a result, or how the assertion affects session/test flow. This is inadequate for a tool whose core behavior is pass/fail validation.

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, front-loaded sentence with no filler. It states the action, target, and matching modes efficiently.

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?

The definition is minimally viable for a simple two-parameter assertion, especially with the schema supplying the exact default. Still, it omits failure behavior and gives no explicit guidance on how the exact flag changes the assertion, so the overall context is not fully complete.

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?

The description adds some meaning beyond the schema by framing 'expected value' as the expected parameter and 'equals or contains' as the behavior controlled by exact. However, it never explicitly maps exact=true to equality and exact=false to containment, and schema description coverage is 0%, so the description does not fully compensate.

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 uses a specific verb ('Assert') and a specific resource ('current URL'), and clarifies the two matching modes: equals or contains. It clearly distinguishes this from page-content assertions like assert_title and assert_text, though it does not explicitly contrast with sibling tools.

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?

There is no guidance about when to use this tool versus alternatives such as get_current_url or assert_page_contains. The context is implied, but no exclusions or decision criteria are provided.

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