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

nekoro-browser-mcp

by zeshuochen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture_screenshot

Capture a browser tab screenshot and return it as a base64 image with size metadata. Specify tab, scale, format, or quality to adjust the output.

Instructions

capture_screenshot() → base64 图 + 尺寸元信息。

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

Input Schema

NameRequiredDescriptionDefault
tabNo
scaleNo
formatNo
qualityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / scale
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / tab
      Added value: +{
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral traits such as side effects, permissions, or limitations. It only states the output format.

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?

The description is extremely concise, with no wasted words. However, it lacks any structural elements beyond a single sentence, which is acceptable given its brevity.

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

Completeness1/5

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

The tool has multiple parameters and a specific return type, but the description does not explain how to use them, what the dimensions refer to, or any edge cases. The description is far from complete.

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

Parameters1/5

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

The schema lists four parameters (tab, scale, format, quality) but the description gives no explanation of their meaning, types, or usage. No semantic information is provided for any parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially repeats the function name and return type, providing no additional clarity about the tool's purpose. The name 'capture_screenshot' makes the purpose obvious, but the description is tautological.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool vs alternatives. No context, prerequisites, or comparison with sibling tools is provided.

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