Skip to main content
Glama

place_master

Places a master instance on a chosen page, using session-injected source/output when paths are omitted. Explicit paths target a project without advancing the session chain.

Instructions

在指定页面上放置母版实例(ReferenceDiagramObject)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node place-master.mjs <src.rp> <out.rp> [--x N --y N]

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive write with no open-world access, so the bar is lower; the description still adds real behavior: explicit paths do not advance the session chain, and the gui-roundtrip evidence registration applies only to verified samples in capabilities.md. The CLI form is also disclosed. Minor gap: it does not say what happens on failure or whether placement is idempotent.

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 core placement semantics and session convention are front-loaded, but the sentence about gui-roundtrip evidence and capabilities.md is internal process jargon that is unlikely to help an agent invoke the tool. The mixed Chinese prose with embedded CLI syntax is dense and requires re-reading.

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 two-parameter mutation tool with no output schema and no enum constraints, the definition covers the essential call shape and session behavior. It still leaves the meaning of the 'session chain' and the host-source assumptions implicit, which matters because the description hinges on those concepts for correct invocation.

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 50%: the session flag is documented inline but the args array items have no descriptions. The CLI line partly compensates by revealing the positional order (src.rp, out.rp, masterName, pageIndex, optional --x/--y), which is useful information not in the schema. It stops short of stating units, ranges for pageIndex, or whether coordinates are required, so it does not fully close the coverage gap.

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 — place a master instance (ReferenceDiagramObject) on a given page — which an agent can distinguish from the sibling create_master. The parenthetical type name adds precision, though it does not explicitly contrast with the other master-related siblings such as set_master_overrides.

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 explains the session-chain convention (omit host source/output for named calls, use session:true with raw args) and notes that multi-source tools still pass an import source, which is genuine invocation guidance. However, it never says when to use this tool rather than create_master or set_master_overrides, so selection against alternatives is left to inference.

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