Skip to main content
Glama
Sign In
pony-browser-mcp

pony-browser-mcp

by pssrh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_get_page_content

Retrieve the current page's content as plain text or HTML, allowing you to read, parse, or process webpage data for further use.

Instructions

Get the content of the current page as text or HTML.

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_get_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: text)
workspaceNoOptional workspace to read from
use_debuggerNoAllow CDP fallback if page CSP blocks scripting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/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 burden of explaining behavioral traits. It only states that content is returned as text or HTML, but does not disclose whether the page may execute scripts, how it handles dynamic content, or any side effects. It lacks detail beyond the basic operation.

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 a single, clear sentence with no wasted words. The verb and object are front-loaded, and the format options are stated efficiently. It is appropriately sized for the tool's simplicity.

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 simple read-only-like tool with full schema coverage, the description adequately states the output, but it lacks usage context and behavioral nuances such as when to use the debugger fallback or how 'current page' is resolved in multi-tab scenarios. No output schema exists, so the description should carry more detail about return values and edge cases.

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 documents all three parameters. The description adds no new meaning beyond what the schema already provides, matching the baseline 3. The mention of text/HTML repeats the format enum without additional semantic value.

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 states a specific action ('Get'), a clear resource ('content of the current page'), and output options ('text or HTML'). It is unambiguous and distinguishes itself from sibling tools like browser_screenshot, browser_get_cookies, or browser_fetch, which serve different purposes.

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?

The description provides no guidance on when to use this tool over alternatives, nor does it mention any conditions or exclusions. It simply describes what the tool does. No sibling comparison or contextual trigger is given, leaving the agent to infer when this tool is appropriate.

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