Quattr

run_dashboard_tile

Read-only

Run one dashboard tile's query, optionally overriding its filters with explicit date ranges, and return its rows.

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": {
      "dashboard_id": "<dashboard_id>",
      "tile_id": "<tile_id>"
    },
    "name": "run_dashboard_tile"
  }
}

Input Schema

Name	Required	Description
`filters`	No	Filter overrides. Keys: the dashboard's filter names or titles (e.g. its date filter), or the tile's own field names; each value replaces the dashboard's default and the tile's saved value. A filter the tile does not use is refused.
`tile_id`	Yes	Tile ID from run_dashboard
`dashboard_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / filters / description

Previous value: -"Filter overrides merged over the tile's own filters"New value: +"Filter overrides. Keys: the dashboard's filter names or titles (e.g. its date filter), or the tile's own field names; each value replaces the dashboard's default and the tile's saved value. A filter the tile does not use is refused."

First observedOct 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that rows are returned and that filter overrides are optional, but says nothing about missing tiles, permission needs, or how overrides interact with the tile's saved state beyond the schema.

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 sentence with the core action front-loaded and no filler, covering action, optionality, and return value.

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?

For a three-parameter read-only tool with no output schema, the description covers what it does, that filters are optional, and that rows come back. Minor gaps remain around dashboard_id's role and error conditions, but nothing essential to invoking it is missing.

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?

Schema coverage is 67% and the filters parameter is already described in detail in the schema, including that unused filters are refused. The description adds only the hint that overrides are typically date ranges, which is slightly narrower than the schema's general filter semantics.

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?

States a specific verb and resource: 'Run one dashboard tile's query ... and return its rows.' The word 'one ... tile' implicitly scopes it below the dashboard-level sibling run_dashboard, 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 implied rather than stated: it is the tool to reach for when a single tile's rows are wanted, with optional filter overrides. There is no explicit when-to-use/when-not guidance or pointer to run_dashboard for whole-dashboard retrieval.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Quattr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?