Skip to main content
Glama

set_master_overrides

Create, update, or clear instance-specific text overrides and embedded PNGs for master instances by ID without changing shared definitions.

Instructions

按实例 ID 创建/更新/清除母版实例的文字覆盖或写入内嵌 PNG,不改共享定义。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node set-master-overrides.mjs source.rp new.rp overrides.json

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "args": "<args>"
    },
    "name": "set_master_overrides"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/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; the description adds the key behavioral fact that changes are confined to the instance and do not alter the shared definition, which explains why clearing an override is not destructive. It also discloses the chain-advancement side effect of session mode versus explicit paths, which is behavior annotations cannot express. It still omits what happens on failure or a partial override, and the 'gui-roundtrip' evidence note is opaque without capabilities.md.

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

Conciseness3/5

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

The purpose is front-loaded and each sentence targets a distinct concern (scope, chain rules, explicit-path rule, evidence restriction, CLI). But the density is high and some fragments, notably '登记证据 gui-roundtrip' and the bare CLI string, read as notes to an insider rather than instructions an agent can act on without extra lookup.

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 chain-aware mutation with only two arguments and no output schema, the description covers the mutation scope and the session-versus-explicit-path decision adequately. It falls short on the actual overrides payload format and on what success or failure looks like, both of which an agent needs before calling a tool whose main input is an untyped string array.

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 only 50%, and the opaque positional `args` array has no schema description at all, so the description must carry it. The session rules plus the CLI line (source.rp, new.rp, overrides.json) effectively reveal the expected argument ordering and what the third argument contains, which is real meaning beyond the schema. The overrides.json payload structure itself remains unspecified.

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 opens with a specific verb set (create/update/clear) applied to a specific resource (master instance overrides by instance ID) and states scope: text overrides or embedded PNG, without touching the shared definition. That scope clause is what distinguishes it from master-editing siblings like create_master or edit_text, 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?

It gives concrete situational rules for the session chain (named invocation omitting host source/output uses the chain; raw args must set session:true and omit those params; explicit paths do not advance the chain) and restricts applicability to verified samples in capabilities.md. However, it never tells the agent when to choose this tool over create_master, place_master, or edit_text, so alternative-selection guidance is absent.

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