Skip to main content
Glama

Report Variables List

report_variables_list
Read-only

Lists report variables with full wire definitions and the report fingerprint required for conflict-checked variable writes; read-only.

Instructions

Resource > Manage variables: report variables with their full wire definitions and the report fingerprint for report_variables_write. 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_variables_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

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares safety, and the trailing 'Read-only' largely restates the annotation. What does add value is the disclosure that results include full wire definitions and the report fingerprint — behavior the annotation cannot convey — but nothing is said about size, pagination, or whether the fingerprint changes between calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence, front-loaded with the resource grouping and ending with the cross-reference to the write tool. Nothing is padded, and even the 'Read-only' redundancy costs only three words.

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 no explanation, and the read-only behavior is covered by annotations. The gap is the sole parameter: for a per-report scoped tool, the agent is not told whether an omitted report_id means 'all reports' or an error, which is material to calling it correctly.

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?

Schema description coverage is 0% for the single optional report_id, and the description never explains it — notably it does not say what omitting the parameter returns. The schema's default of null and its type make the basic contract readable, and the description does clarify what the call yields, so this sits just above a bare minimum.

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 the concrete resource (report variables) and the payload (full wire definitions plus the report fingerprint), and explicitly contrasts itself with the sibling it feeds, report_variables_write. The only weakness is that 'list' is implied by the name rather than the verb in the description, but an agent can still tell what it returns.

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?

Naming 'the report fingerprint for report_variables_write' implicitly tells the agent this is the read step before a write, which is real workflow guidance. However, there is no explicit when-to-use/when-not statement, and no guidance on whether to call this versus inspecting report content through another route.

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