Skip to main content
Glama

Blends Rename

blends_rename
Destructive

Rename up to 100 report-local data views by ID in one guarded report write, preserving queries, joins, fields, IDs, bindings, and unknown values. Preview changes by default before applying.

Instructions

Rename 1-100 report-local data views by ID, in one guarded report write.

Get the fingerprint from blends_list. Changes only datasourceBlock.name; preserves queries, joins, fields, IDs, bindings and unknown values. Names need not be unique. Does not rename/create/publish datasource assets. Missing historical input sources do not prevent this label-only edit. Preview by default. Applied edits have durable read-back and operation_restore.

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_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.6/5.0
Behavior5/5

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

Beyond the destructive/not-read-only annotations, it discloses the exact blast radius (only datasourceBlock.name; queries, joins, fields, IDs, bindings and unknown values preserved), the dry-run default, and the recovery path ("durable read-back and operation_restore"). It even removes a likely blocker by noting missing historical input sources do not prevent the edit.

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?

The action and its scope are front-loaded, and the following sentences each add distinct information (invariants, exclusions, prerequisites, recovery). It is dense but slightly list-like, with a couple of clauses that could be tightened.

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 guarded batch mutation with an output schema and safety annotations present, the description covers prerequisites, what is and isn't modified, preview behavior, and rollback. Nothing an agent needs to invoke it safely is missing.

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 must carry the burden and largely does: it bounds changes to 1-100 entries keyed by blend_id, explains that expected_report_content_fingerprint comes from blends_list, and flags the preview default for dry_run. report_id is only implicitly covered by "report-local" / "one guarded report write," leaving one parameter under-explained.

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?

"Rename 1-100 report-local data views by ID, in one guarded report write" states a specific verb, resource, batch bound, and transactional scope. It also distinguishes the target from similarly named siblings by clarifying these are report-local blends, not datasource assets.

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?

It gives a concrete prerequisite ("Get the fingerprint from blends_list") and states the default mode ("Preview by default"), plus an exclusion: it does not rename/create/publish datasource assets. It stops short of naming a specific sibling to use for datasource renaming, so the routing is implied rather than explicit.

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