Skip to main content
Glama

rename_custom_style

Rename a custom style across an RP/RPLIB project and cascade the new name to all linked MatchInfo and StyleCache records so style references stay consistent.

Instructions

按样式身份级联改名,更新所有记录的 MatchInfo 与 StyleCache 名称。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node rename-custom-style.mjs <source.rp|rplib> <output.rp|rplib>

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world mutation, and the description adds real context beyond them: the rename cascades to every record's MatchInfo and StyleCache, and it is only valid for verified samples in capabilities.md. It stops short of stating reversibility or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by invocation semantics and the CLI signature. Dense but every sentence carries information; the evidence-registration sentence is terse to the point of being cryptic.

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 cascading mutation with no output schema, the definition covers what is changed, which invocation modes exist, and where the tool is valid. Missing only return/failure detail, which is a minor gap given the tool's narrow verified-sample scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema only explains the session flag; the description supplies the missing semantics of the oneOf branches – which parameters to omit for session-chain use, that multi-source tools keep the import source, and that explicit paths do not advance the chain. That is genuine meaning beyond the schema.

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 and resource plus the mechanism: cascade-rename by style identity, updating MatchInfo and StyleCache names in all records. That clearly separates it from widget-level siblings like rename_widget, though no sibling is named explicitly.

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?

The description explains invocation modes (named call omits host source/output to use the session chain; raw args need session:true; explicit paths do not advance the chain), but it never says when to pick this tool over related style tools such as set_widget_style. Usage context is implied rather than stated against alternatives.

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