Skip to main content
Glama

Reports List

reports_list
Read-only

Lists report tabs open in the MCP Chrome profile, showing each one's mode and which tab is active so you can target the right report before editing.

Instructions

List report tabs open in the MCP Chrome profile with mode and which one is active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety needs no restating. The description does add real context beyond that: the listing is scoped to the MCP Chrome profile (live browser state, not API-backed content) and each entry carries a mode plus an active flag. It stops short of saying what happens when no profile/tabs exist or what 'mode' denotes.

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 front-loaded sentence with no filler; every clause (verb, resource, scope qualifier, returned fields) carries information. No restructuring would make it easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and no parameters, the description needn't document return shape, and it correctly stays brief while establishing the browser-profile scope. The only residual gap is the undefined term 'mode' and the unstated condition of no open tabs, both minor for a zero-argument read.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly introduces no parameter talk, keeping the definition clean.

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 a specific verb ("List") and a specific resource ("report tabs open in the MCP Chrome profile"), plus the returned attributes (mode, active tab). That scope is narrow enough that it is not confusable with the sibling `datasources_list`/`filters_list`-style account-resource listers, though no sibling is named explicitly.

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 only implied: the phrasing "open in the MCP Chrome profile" suggests it reports live browser tab state rather than persisted Looker content, which is the key selection signal. There is no explicit when-to-use statement, no exclusion of alternatives, and no stated prerequisite that a Chrome session must be running.

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