Skip to main content
Glama

Blends Inputs Rename

blends_inputs_rename
Destructive

Renames up to 100 blend input table labels by setting query.displayName for exact input paths; preview-first edits can be applied via guarded report write and restored.

Instructions

Rename 1-100 input table labels using exact paths from blends_list.

Changes only query.displayName. Empty name removes the custom label and restores the native default; maximum 100 UTF-16 code units. Duplicate names are permitted, repeated target inputs are not. Preserves source IDs, concept IDs, fields, joins, filters and unknown properties. Historical missing sources do not prevent label-only edits. Preview by default; one guarded report write and operation_restore for applied changes.

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": {
      "changes": "<changes>",
      "expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
    },
    "name": "blends_inputs_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
dry_runNo
report_idNo
expected_report_content_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the destructiveHint=true / readOnlyHint=false annotations: it names exactly what is mutated (query.displayName), the empty-name behavior that restores native defaults, the UTF-16 length cap, duplicate-name vs. duplicate-target rules, and what is explicitly preserved (source IDs, concept IDs, fields, joins, filters). It also discloses the preview-by-default safety model and the single guarded report write.

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?

Front-loads the verb, resource, and path requirement, then layers constraints. Every clause carries information, though the telegraphic fragment style ('Duplicate names are permitted, repeated target inputs are not') takes effort to parse.

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?

Output schema exists so return values need no explanation, and the mutation semantics plus recovery path are well covered. The remaining gap is how an agent obtains the required fingerprint and report_id before calling.

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?

With 0% schema description coverage the description carries the load, and it does explain the `changes` array well (1-100 entries, name semantics, empty name, uniqueness of target inputs) and implies dry_run via 'Preview by default'. It does not explain `report_id` or what `expected_report_content_fingerprint` guards, leaving two of four parameters undocumented in both places.

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?

States a specific verb and resource ('Rename 1-100 input table labels'), bounds the scope, and points at blends_list as the source of the exact paths. This clearly separates it from blends_rename, which operates on the blend itself rather than its input labels.

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

Usage Guidelines4/5

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

Gives a concrete prerequisite ('exact paths from blends_list') and describes the operating mode ('Preview by default; one guarded report write and operation_restore for applied changes'). It lacks an explicit when-not-to-use statement or a direct pointer to the blend-level rename alternative.

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