Skip to main content
Glama

调整字体排版

xiumi_set_typography

Adjust font size, line spacing, letter spacing, and text color for body paragraphs or all text to unify article typography.

Instructions

批量调整正文(或全部文本)的字号、行距、字距和颜色,用于统一全文排版。scope=body 只改长段落,scope=all 改包括标题在内的所有文本槽。

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

Input Schema

NameRequiredDescriptionDefault
colorNo文字颜色,如 #333333
scopeNobody 仅正文段落(默认),all 全部文本
minCharsNobody 模式下视为正文的最少字符数,默认 25
lineHeightNo行距倍数,如 1.9
fontSizePercentNo字号,百分比(100 = 16px)
letterSpacingPxNo字距,单位 px,如 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the operation is a batch mutation over text slots and that body mode skips short paragraphs, but it says nothing about reversibility, whether an article must be open, or what happens to text that does not match the criteria.

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?

One tight sentence, verb-first, followed by the single disambiguation that matters (body vs all). Nothing is repeated and nothing is padded.

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?

With six optional parameters, no output schema and no annotations, the definition covers purpose and scope but leaves out return behaviour, preconditions, and how this interacts with sibling text tools. Adequate to invoke, not complete enough to predict the result.

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 coverage is 100%, so all six parameters already carry their own descriptions and the baseline is 3. The description only re-states the scope semantics (body = long paragraphs, all = including headings) that the enum already expresses, adding no new syntax or format detail.

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?

A specific verb+resource: batch-adjusts font size, line height, letter spacing and color of body (or all) text. It clearly distinguishes its own two modes (scope=body vs scope=all) but never contrasts itself with sibling tools such as xiumi_fill_text, so a 4 rather than 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 Guidelines4/5

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

"用于统一全文排版" gives the intent, and the scope clause tells the agent which mode to pick: body for long paragraphs only, all when headings should be normalised too. There are no explicit exclusions or prerequisites (e.g. must an article be open first), which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.