Skip to main content
Glama
luno-cms

LUNO — AI Backend Platform

Official
by luno-cms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_master_record

Idempotent

Update a master record using its entity and record IDs. Edit label, value, sort order, parent, data, or color; requires user JWT with edit rights, and agent API keys are rejected.

Instructions

マスタレコードを更新。必須: entityId, recordId。任意: label, value, sortOrder, parentRecordId, data, color（#RRGGBB。null で消す）。エージェント API キーでは不可（401 — ユーザ JWT + 編集権限が必要）。identifier（slug / value）の変更は rename_master_record_slug → propose_change。並び替え・色の一括は apply_master_blueprint を使う。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo追加 JSON。既知キー以外の拡張データ
colorNo任意の #RRGGBB。null で色を消す
labelNo表示ラベル（string または { ja, en } 等の locale map）
valueNo選択肢 value。select/radio snapshot に入れる文字列
entityIdYesマスタエンティティ UUID（list_master_entities の id）
recordIdYesマスタレコード UUID（list_master_records / create_master_record の id）
sortOrderNo並び順（小さいほど先）
parentRecordIdNo親レコード UUID。ルートは null。階層マスタのみ

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPrimary resource UUID for the next tool call
okNo
nameNo
slugNoURL slug when the resource has one
itemsNoList rows; pass item.id to get_*/update_*
statusNoResource or revision status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • addedInput schema / properties / color
      Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^#[0-9a-fA-F]{6}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "任意の #RRGGBB。null で色を消す"
+}
  2. Changed6 schema fields changedv0.1.4
    • addedInput schema / properties / data / description
      Added value: +"追加 JSON。既知キー以外の拡張データ"
    • addedInput schema / properties / label / description
      Added value: +"表示ラベル（string または { ja, en } 等の locale map）"
    • addedInput schema / properties / parentRecordId / description
      Added value: +"親レコード UUID。ルートは null。階層マスタのみ"
    • addedInput schema / properties / sortOrder / description
      Added value: +"並び順（小さいほど先）"
    • addedInput schema / properties / value / description
      Added value: +"選択肢 value。select/radio snapshot に入れる文字列"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "definitions": {
+    "__schema0": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        },
+        {
+          "items": {
+            "$ref": "#/definitions/__schema0"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {
+            "$ref": "#/definitions/__schema0"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      ]
+    }
+  },
+  "properties": {
+    "id": {
+      "description": "Primary resource UUID for the next tool call",
+      "type": "string"
+    },
+    "items": {
+      "description": "List rows; pass item.id to get_*/update_*",
+      "items": {
+        "additionalProperties": {
+          "$ref": "#/definitions/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "slug": {
+      "description": "URL slug when the resource has one",
+      "type": "string"
+    },
+    "status": {
+      "description": "Resource or revision status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are minimal (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds critical behavioral context beyond those: agent API keys are rejected with 401, color accepts null to clear the value, and identifier changes require a different workflow. This gives the agent important operational details that annotations do not convey.

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?

The description is compact and front-loaded: the core action, required params, auth restriction, and routing to alternatives are all stated in a few sentences with no filler. Every sentence carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, nested objects, and an output schema, the description covers the essential operational context: required vs optional params, auth constraints, when to delegate to siblings, and the null behavior for color. Since an output schema exists and annotations cover idempotency/safety, nothing critical is missing.

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 description coverage is 100%, so parameter semantics are already fully documented. The description restates required vs optional params and mentions the color null behavior, which mirrors the schema. It adds no significant new meaning beyond a concise summary, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('マスタレコードを更新' – update master record) and immediately enumerates the required and optional parameters. It also distinguishes itself from related tools by naming rename_master_record_slug and apply_master_blueprint for identifier changes and batch operations, so an agent can tell what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly says when NOT to use this tool: identifier (slug/value) changes should go through rename_master_record_slug → propose_change, and batch sorting/color should use apply_master_blueprint. It also states the auth requirement (user JWT + edit permission, agent API key rejected with 401), giving clear selection criteria.

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