Skip to main content
Glama
Sign In
mcp-web-print-pdf

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

switchTabsVisibility

Control which of the five client tabs are visible—BasicInfo, Printers, Logs, Run Example, and ContactUs—and reset all to default visibility.

Instructions

切换客户端 5 个标签页的显隐；reset: true（或 tabs: null）= 全部恢复默认

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

Input Schema

NameRequiredDescriptionDefault
tabsNo要改的标签页；传 null 恢复默认
resetNotrue = 恢复默认，等价于 tabs: null

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

B3.3/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 behavioral burden. It discloses scope (5 tabs) and the reset behavior, but is silent on the two behaviors that matter most for a mutation tool: whether a partial `tabs` array leaves unlisted tabs untouched or replaces the whole set, and whether the change persists across restarts.

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 semicolon-delimited line with the core action front-loaded and the reset shortcut immediately after. Nothing is wasted or buried.

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?

Only two optional parameters and no output schema, so the bar is modest, but with no annotations at all the description should still say what partial-array updates do and whether state survives reloads. It covers the reset path but not the default/merge semantics.

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?

Schema description coverage is 100%, with both `tabs` and `reset` documented and enums visible in the schema. The description restates the reset/tabs-null equivalence already present in the schema, adding no new parameter semantics, so baseline 3 applies.

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?

States a specific verb+resource with scope: switch visibility of the client's 5 tabs, and enumerates that there are exactly 5. It does not differentiate from the nearest sibling (setContactUsTabInnerHtml), but that sibling has a clearly different purpose, so an agent can distinguish them without the description.

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

Usage Guidelines3/5

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

Usage is only implied – the description says what it toggles but never states when an agent should call it versus leaving tabs alone, nor any preconditions. Implied usage only, so 3 is the ceiling.

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