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

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

setTitle

Sets the client window title to a custom value and restores the default when reset is true or title is null.

Instructions

设置客户端窗口标题；reset: true（或 title: 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": "setTitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNotrue = 恢复默认，等价于 title: null
titleNo新标题；传 null 恢复默认

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the restore-default behavior, which is real behavioral context, but says nothing about persistence, whether the title survives reloads, or what happens with an empty string—gaps that matter for a mutation tool with no 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?

A single compact sentence that front-loads the action and then the reset escape hatch. Nothing is wasted and the key semantic detail appears immediately.

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

Completeness4/5

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

For a two-parameter, no-output, no-annotation tool, the description covers the action and the reset case adequately. Minor incompleteness remains around persistence and edge cases of the title value.

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%, so both parameters are already documented. The description repeats the reset/title:null equivalence without adding meaning such as empty-string handling or title length limits, so the baseline of 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?

The description states a specific verb and resource: setting the client window title, which is unambiguous against siblings like setThemeColor or switchTabsVisibility. It doesn't explicitly name or differentiate itself from any sibling, which keeps it just short of a 5.

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?

It explains the reset path (reset: true or title: null restores the default), which is usage-relevant, but never states when to use this tool versus doing nothing or whether the change is scoped to a session. Usage is implied rather than guided.

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