Skip to main content
Glama
WhiteNightShadow

camoufox-reverse-mcp

get_page_info

Retrieve the current page's URL, title, and viewport size for browser state inspection.

Instructions

Get current page URL, title, and viewport size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the get_page_info tool. Gets the active page, retrieves URL, title, and viewport dimensions.
    @mcp.tool()
    async def get_page_info() -> dict:
        """Get current page URL, title, and viewport size."""
        try:
            page = await browser_manager.get_active_page()
            viewport = page.viewport_size or {}
            return {
                "url": page.url, "title": await page.title(),
                "viewport_width": viewport.get("width"),
                "viewport_height": viewport.get("height"),
            }
        except Exception as e:
            return {"error": str(e)}
  • Registration via import in server.py: the navigation module (containing get_page_info) is imported so that the @mcp.tool() decorator registers it with the FastMCP server.
    from .tools import navigation      # noqa: E402, F401  — browser control + page interaction
  • Helper method in BrowserManager used by get_page_info to retrieve the active Playwright page.
    async def get_active_page(self) -> Page:
        """Get the currently active page, launching the browser if needed."""
        await self._ensure_browser()
        if self.active_page_name and self.active_page_name in self.pages:
            return self.pages[self.active_page_name]
        raise RuntimeError("No active page available. Call launch_browser first.")
  • The @mcp.tool() decorator registers get_page_info as an MCP tool with the FastMCP server.
    @mcp.tool()
    async def get_page_info() -> dict:
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only lists what is returned, but does not state whether the tool requires an active page, has side effects, or is read-only.

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 sentence that is front-loaded with the purpose. Every word earns its place; no wasted text.

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 tool with no parameters and no output schema, the description is minimally adequate but lacks contextual details such as safety guarantees (read-only), required state (active page), or relation to siblings.

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 input schema has zero parameters (100% coverage). According to guidelines, baseline is 3 when schema description coverage is high. The description does not add parameter info, but none is needed.

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 clearly states the verb 'Get' and the resource 'current page URL, title, and viewport size'. It is specific and distinguishes the tool from siblings like navigate, click, or take_screenshot.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WhiteNightShadow/camoufox-reverse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server