Skip to main content
Glama

Field Overrides List

field_overrides_list
Read-only

Lists a report's field overrides, including display names, IDs, original fields, and datasource IDs, plus the fingerprint required to write override changes safely.

Instructions

Resource > Manage field names and IDs: the report's field overrides ({displayNameOverride, idOverride, originalId, originalName, datasourceId}) and the fingerprint field_overrides_write needs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "field_overrides_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: the exact shape of the returned override records and the cross-tool dependency on the fingerprint value. It omits pagination or scope behavior, but for a simple read that is a modest gap.

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?

It is one sentence with no filler, but the 'Resource > Manage field names and IDs' prefix reads like a nav breadcrumb and the trailing 'fingerprint field_overrides_write needs' clause is grammatically compressed to the point of being cryptic.

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 needn't be explained, and annotations cover the safety profile; the useful addition is the dependency on field_overrides_write. What remains missing is any statement about the optional report_id parameter and its default behavior, which is the main thing an agent must get right to call this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single report_id parameter, and the description never mentions it. With no explanation of what happens when report_id is null (the default), an agent cannot tell whether omitting it targets a default report or fails.

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 identifies the resource concretely ('the report's field overrides') and enumerates the fields returned, so an agent knows it retrieves override mappings rather than writing them. The verb is only implied by the name and the 'Resource > Manage field names and IDs' taxonomy prefix is thin, but the read nature is unambiguous against field_overrides_write.

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 hints at the intended workflow by saying this returns 'the fingerprint field_overrides_write needs', which implies fetching before writing. It never states when not to use it, nor whether it is a prerequisite or merely optional context for the write tool.

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