Skip to main content
Glama
Sign In
@ainative/browser-mcp

@ainative/browser-mcp

Official
by AINative-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

browser_validate

Read-onlyIdempotent

Verify web page content or state using natural language assertions. Check that specific content exists, a form was submitted, or a page reached an expected state.

Instructions

Validate content or state on a web page. Use when you need to assert that specific content exists, a form was submitted, or a page reached an expected state. (25 credits)

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>",
      "assertion": "<assertion>"
    },
    "name": "browser_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the web page to validate
assertionYesNatural language assertion to validate (e.g. "The page contains a success message")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds purpose and examples but does not disclose behavioral details like what happens when validation fails or the return format. This is adequate but not rich.

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?

The description is two concise sentences with no fluff. It includes the credit cost and relevant usage context, earning its place for each word.

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?

Given the tool's simplicity, complete parameter documentation, and strong annotations, the description is mostly sufficient. However, the absence of an output schema means the description should ideally indicate the result type (e.g., boolean pass/fail), which it does not, so a small gap remains.

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%, so the schema already documents both parameters. The description adds examples of assertions but does not provide additional parameter-level nuance beyond what the schema states, meeting the baseline of 3.

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

Purpose5/5

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

The description uses a specific verb 'validate' and resource 'web page', and provides concrete examples like 'assert that specific content exists, a form was submitted'. This clearly distinguishes it from sibling tools like browser_act or browser_extract.

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?

The description explicitly states when to use it: 'Use when you need to assert that specific content exists, a form was submitted, or a page reached an expected state.' However, it does not mention when not to use it or name alternative tools, so it falls just short of a 5.

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