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

mcp-web-print-pdf

by weixiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

setContactUsTabInnerHtml

Sets the client's Contact Us page HTML to customize its content; pass reset or null to restore the default.

Instructions

设置客户端「联系我们」页面的 HTML；reset: true（或 html: 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": "setContactUsTabInnerHtml"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNo新的 HTML；传 null 恢复默认
resetNotrue = 恢复默认，等价于 html: null

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A3.9/5.0
Behavior3/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 the key reset behavior (reset: true or html: null restores default), but does not mention permissions, validation/sanitization, whether existing content is overwritten, or response 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?

A single compact sentence with the primary action and reset behavior front-loaded. There is no redundant or filler text.

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 two-parameter setter with full schema coverage, the core operation and reset path are covered. However, with no annotations and no output schema, it should say more about mutation safety, permissions, or expected response to be 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?

Schema description coverage is 100%, and the schema already documents both parameters. The description restates the reset/null equivalence rather than adding new syntax, format, or validation details beyond the schema.

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

Purpose5/5

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

The description states a specific verb (设置/set) and a precise resource (客户端「联系我们」页面的 HTML), making it clearly distinct from sibling tools like setTitle, setThemeColor, and the print-oriented tools.

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

Usage Guidelines4/5

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

It gives clear context for use: setting the Contact Us page HTML, with reset semantics. There are no competing alternatives to route between, but it does not explicitly state when not to use it or any prerequisites.

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