Skip to main content
Glama
Sign In
bwiki-mcp

bwiki-mcp

by putaojuju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bwiki_screenshot

Capture BWIKI page screenshots by selecting full-page or specific elements, and choose where to save them.

Instructions

截取BWIKI页面截图。

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

Input Schema

NameRequiredDescriptionDefault
fullPageNo是否截取整个页面
savePathNo保存路径
selectorNo截取特定元素

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the screenshot is saved to savePath, returned as data, or if any side effects occur. This leaves the agent uncertain about the tool's behavior.

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, concise sentence with no wasted words. It effectively communicates the core purpose in a front-loaded manner, ideal for a simple tool.

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?

Although the schema covers parameter details, the description lacks contextual information about the return value or how the screenshot is delivered (saved vs. returned). With no output schema, this is a notable gap, and the brevity leaves the agent without enough context to use the tool confidently.

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 already provides descriptions for all three parameters (fullPage, savePath, selector), so the baseline is appropriate. The tool description adds no additional parameter semantics beyond what the schema already states.

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 tool's action with a specific verb and resource: '截取BWIKI页面截图' (capture a BWIKI page screenshot). However, it does not differentiate from the sibling tool bwiki_snapshot, which could be almost synonymous, so it misses the chance to distinguish.

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?

There is no guidance on when to use this tool instead of alternatives such as bwiki_snapshot or bwiki_get_content. The description only states the action without any context, exclusions, or recommended scenarios.

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