Skip to main content
Glama
hyperpolymath

BoJ-server

by hyperpolymath
OverviewSchemaRelated ServersScoreDiscussions

boj_browser_screenshot

Capture browser page screenshots to document content, troubleshoot issues, or share visual information from web applications.

Instructions

Take a screenshot of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • mcp-bridge/main.js:689-700 (handler)
    Handler block for browser-related tools including 'boj_browser_screenshot'. It invokes 'browser-mcp' cartridge with the action 'screenshot'.
    case "boj_browser_navigate":
case "boj_browser_click":
case "boj_browser_type":
case "boj_browser_read_page":
case "boj_browser_screenshot":
case "boj_browser_tabs":
case "boj_browser_execute_js": {
  const action = toolName.replace("boj_browser_", "");
  const result = await invokeCartridge("browser-mcp", { action, ...args });
  sendResult(id, { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] });
  break;
}
  • mcp-bridge/main.js:493-500 (registration)
    Registration of the 'boj_browser_screenshot' tool in the tool list provided to the MCP client.
    tools.push({
  name: "boj_browser_screenshot",
  description: "Take a screenshot of the current page",
  inputSchema: {
    type: "object",
    properties: {},
  },
});

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether this is a read-only operation, what format the screenshot returns (e.g., image data, file path), potential side effects, or any rate limits. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose with no unnecessary words. It's front-loaded and appropriately sized for a simple tool, earning its place without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It lacks details on output format (e.g., image data type), behavioral context, and usage guidelines, making it insufficient for an agent to fully understand how to invoke and interpret results.

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 has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here, but doesn't compensate for any gaps since there are none. Baseline is 4 for zero parameters.

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 clearly states the action ('Take a screenshot') and the target ('of the current page'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'boj_browser_read_page' which might also involve page content retrieval, missing full sibling differentiation.

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 versus alternatives. It doesn't mention prerequisites (e.g., needing an active browser page), exclusions, or compare it to similar tools like 'boj_browser_read_page', leaving the agent to infer usage context.

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/hyperpolymath/boj-server'

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