Skip to main content
Glama

browser_source_probe

Read-onlyIdempotent

Reload authenticated development pages to detect invalid resource references in original HTML, excluding boot data for targeted debugging.

Instructions

Reload the authenticated development page and inspect only invalid resource references in the original HTML; excludes boot data.

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": "browser_source_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: the page must be authenticated, the reload happens first, and inspection is against original HTML rather than rendered DOM. It still says nothing about what results look like or what happens on failure to load, so it adds context but not a full behavioral picture.

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

Conciseness4/5

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

One dense sentence with the action and scope front-loaded and no filler. It loses a point only because terms like 'boot data' and 'original HTML' are unexplained jargon that a caller must interpret.

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 tool is simple (zero parameters) and has no output schema, but that means the description is the only place a caller can learn what the probe returns and how invalid references are reported. It covers what is inspected but not the shape or scope of the result, leaving a gap for a tool whose entire value is its output.

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

Parameters4/5

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

The tool takes zero parameters, so there are no parameter semantics to explain and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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 opens with a concrete verb and resource: reload the authenticated development page and inspect invalid resource references in the original HTML. It is clearly narrower than generic siblings like browser_diagnostics or browser_snapshot, but it never names or contrasts them explicitly, leaving the agent to infer differentiation.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool is for finding broken resource references in server-returned HTML, and the 'excludes boot data' clause scopes the inspection. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for related checks such as diagnostics or snapshot.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.