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

nekoro-browser-mcp

by zeshuochen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

page_info

Retrieves the title and URL of a browser tab. Specify a tab index to target a specific tab, or leave blank to get the active tab's page information.

Instructions

page_info() → {title, url}。tab 不传打当前活动标签。

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

Input Schema

NameRequiredDescriptionDefault
tabNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / tab
      Added value: +{
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The description discloses that omitting 'tab' targets the current active tab, which is a helpful behavioral detail. However, with no annotations provided, it does not mention read-only status, error handling, or behavior with invalid tab IDs, leaving the description to carry a heavier burden than it does.

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 extremely concise: a return signature and a default-value note. Every word is purposeful, and the key information is front-loaded.

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 tool with one optional parameter, the description provides the core return shape and a key default. However, it lacks context on how to specify the tab integer (e.g., index or ID) and what happens on invalid input. Given the absence of an output schema and annotations, this is adequate but not fully complete.

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 schema lists 'tab' as an optional integer with no description. The description adds that omitting it targets the active tab, providing meaning beyond the schema. It does not clarify what integer values represent (e.g., tab ID from list_tabs), but for a single parameter, this is partial compensation.

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 specifies the return value as {title, url}, indicating a tool that retrieves page metadata. It implicitly distinguishes from sibling content-fetching tools like get_markdown or page_text, though it does not explicitly name alternatives.

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 is given about when to use this tool versus siblings. The only usage note is the default behavior of the 'tab' parameter ('tab 不传打当前活动标签'), which addresses invocation but not tool selection.

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