Skip to main content
Glama

Report Content Get

report_content_get
Read-only

Retrieve saved report-level content and the fingerprint required for conflict-checked patching: attributes, theme, datasource aliases, parameters, field overrides, and components. Read-only.

Instructions

Saved report-level content (attributes, properties, theme and every resource: datasource aliases, parameters, dimension colors, field overrides, report-level components) with the fingerprint report_patch needs. Read-only.

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": "report_content_get"
  }
}

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.2/5.0
Behavior3/5

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

readOnlyHint=true is already in the annotations, and 'Read-only' merely restates it. The description does add genuinely useful context: the scope of what is returned and the presence of the fingerprint used by report_patch. However, with annotations covering the safety profile and an output schema covering the return shape, this is add-value-but-shallow territory rather than rich behavioral disclosure.

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?

Nothing is wasted: a single dense sentence that front-loads what is returned and ends with the downstream dependency. The parenthetical enumeration is long but each item is concrete and the structure keeps the key fact, the fingerprint, at the end.

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?

The output schema covers the return shape, so the description need not explain return values, and the annotations cover the safety profile. The remaining gap is the null/default semantics of report_id, which neither the schema nor the description explains.

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 parameter report_id, and the description does not explain it at all. It never clarifies what an omitted, null, or default report_id means (for example, whether it targets the current report), which is the one semantic an agent most needs for this schema.

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 names the specific resource returned: saved report-level content, with an explicit enumeration (attributes, properties, theme, datasource aliases, parameters, dimension colors, field overrides, report-level components). The verb is implicit in the name, but the phrase 'with the fingerprint report_patch needs' distinguishes it from report_patch and other siblings by tying it to a downstream need.

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?

Usage is implied rather than stated: mentioning that it provides the fingerprint report_patch needs hints at a read-then-patch workflow, but the description never says 'call this before report_patch' or when not to call it. No alternatives are named and no prerequisites are given.

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