Set Typora's active light and dark theme by providing theme names, updating user preferences.
Set the active standard theme or dark theme in Typora's user preferences.
| Name | Required | Description | Default |
|---|---|---|---|
| theme | No | Theme name for standard/light mode (e.g. 'github.css', 'newsprint.css'). | |
| dark_theme | No | Theme name for dark mode (e.g. 'night.css'). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It discloses that the tool mutates Typora's user preferences, but it does not state whether themes must already be installed, whether omitted parameters leave the corresponding mode unchanged, whether changes are reversible, or what happens on invalid input.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. It immediately communicates action, target, and scope, and does not repeat schema content. It is appropriately concise for a simple two-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple setter, the description plus fully documented schema parameters is close to sufficient. However, the absence of annotations and an output schema leaves open key invocation details such as whether themes must exist beforehand and what a successful call returns. These gaps are meaningful but not disabling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both 'theme' and 'dark_theme' with light/dark-mode semantics and examples. The description's phrase 'standard theme or dark theme' loosely maps to those parameters but adds no new detail about valid names, fallback behavior, or the interaction between the two optional parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific action verb ('Set') and names the exact resource and scope: 'active standard theme or dark theme in Typora's user preferences.' This clearly distinguishes it from sibling tools like typora_list_themes, typora_install_theme, and typora_get_theme_css.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given for when to use this tool versus alternatives. It does not mention prerequisites such as using typora_list_themes to find valid installed themes or typora_install_theme before setting a custom theme. The only implied context is the purpose statement, which is not enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.