Skip to main content
Glama

Field Overrides Write

field_overrides_write
Destructive

Override field display names and IDs across a report, and remove overrides, with shared ID overrides enabling one filter or control to apply across datasources without altering them.

Instructions

Override a field's display name and/or ID across this report (Manage field names and IDs). upserts: {datasource_id, field (source field name), display_name?, id_override?}; deletes: {datasource_id, field}. Giving fields of several datasources the same id_override lets one filter or control apply to all of them. The datasource itself is unchanged. Journalled, verified, restorable.

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": {
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "field_overrides_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
deletesNo
dry_runNo
upsertsNo
report_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds real context on top: "Journalled, verified, restorable" tells the agent the mutation is recoverable, and "The datasource itself is unchanged" bounds the blast radius. That goes beyond the annotation set without contradicting it, though it never says what a delete actually removes or how verification failures surface.

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?

Dense and front-loaded: the core action comes first, then the payload shapes, then the cross-datasource tip, then the reversibility note. The parenthetical "(Manage field names and IDs)" and the clipped "Journalled, verified, restorable" are slightly cryptic but earn their space.

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?

An output schema exists, so return values need not be described, and the nested payloads are covered. The gap is the required concurrency token and the dry_run default, both central to safely invoking a destructive upsert/delete tool.

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?

With schema coverage at 0%, the description carries the burden, and it does decode the two nested payload shapes (datasource_id, field, optional display_name and id_override). However it leaves the single required parameter expected_fingerprint entirely unexplained, and ignores dry_run and report_id, which are consequential for a destructive tool.

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 states a specific verb and resource ("Override a field's display name and/or ID across this report") and immediately scopes it with "The datasource itself is unchanged," so an agent knows this is a metadata-only override rather than a data edit. It does not explicitly point at field_overrides_list as the read counterpart, so sibling differentiation is implied by the verb rather than stated.

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 clarifies the two payload modes (upserts versus deletes) and gives one genuine usage insight: reusing the same id_override across datasources makes a single filter apply to all of them. It gives no when-to-use versus when-not guidance, does not mention that dry_run defaults to true, and does not say how to obtain the required expected_fingerprint.

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