Skip to main content
Glama
Sign In
Browser Runtime MCP

Browser Runtime MCP

by MakiDevelop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_page_info

List all pages the extension is currently tracking, showing URL, title, and last activity time, plus buffer statistics.

Instructions

列出 extension 目前追蹤到的頁面（URL + title + 最後活動時間）以及緩衝區統計。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/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 full behavioral disclosure burden. It states that the tool lists currently tracked pages and buffer statistics, indicating a read-only operation, but it does not explicitly confirm safety, permissions, or side effects. It could benefit from stating that this is a non-mutating inspection tool.

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, well-structured sentence that starts with the action verb and includes key output components. It is concise with no unnecessary wording.

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 zero-parameter, read-only listing tool, the description provides adequate context: it specifies the exact data returned (pages with URL/title/last activity, buffer stats) and implies the current state. Without an output schema, the description covers essential return values, though it could elaborate on the format of buffer statistics.

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?

There are no parameters, and the schema is empty, so parameter semantics are trivially covered. The description adds context about the return payload (URL, title, last activity, buffer stats), which clarifies the tool's output without needing parameter explanations. Baseline 4 is appropriate.

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 the specific verb '列出' (list) and clearly identifies the resource as pages tracked by the extension, including URL, title, and last activity time, plus buffer statistics. This distinguishes it from sibling tools like get_browser_errors and get_console_logs, which address errors and logs respectively.

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?

The description does not provide explicit when-to-use or alternative guidance. It clearly explains that the tool returns page tracking info, implying it is used when page data is needed, but no exclusions or alternative tools are mentioned.

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