Skip to main content
Glama

Page Filter Inheritance

page_filter_inheritance
Read-only

Resolve filter inheritance for every page component, including saved and runtime boundaries, nested-group scope, and validator compatibility against loaded schemas.

Instructions

Resolve saved and current runtime filter inheritance for every page component.

The saved view walks report → page → outer/inner groups → component, applies every inheritFilters boundary, and reports nested-group controlStatePassThrough scope. The native view adds provenance layers, runtime cross-filters, validator compatibility for every saved filter against each loaded component schema. Effective runtime definitions are reported as not_exposed_by_bundle: the current bundle no longer exports that resolver. It fails on malformed/ambiguous group ownership, cycles, dirty/stale editor state, or a report change during inspection. Read-only; compatibility does not prove backend query results.

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": {
      "page_id": "<page_id>"
    },
    "name": "page_filter_inheritance"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.1/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 substantial context beyond that: failure conditions (malformed/ambiguous group ownership, cycles, dirty/stale editor state, report change mid-inspection), the not_exposed_by_bundle outcome, and the caveat that compatibility does not prove backend query results. This is rich behavioral disclosure, though the dense jargon slightly reduces accessibility.

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?

The content is front-loaded and every sentence carries information, but the prose is dense and jargon-heavy (controlStatePassThrough, provenance layers, not_exposed_by_bundle), making it harder to parse than necessary. It is efficient but not clean.

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 failure modes are well covered. However, for a tool with two undocumented parameters and two distinct resolution modes, the absence of any parameter guidance leaves a real completeness gap.

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 two parameters, so the description must carry the burden, yet it never explains page_id or report_id (required vs optional, format, or how report_id interacts with the saved/native views). The parameter meaning is left entirely to the bare schema types.

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: resolving saved and current runtime filter inheritance for every page component, and distinguishes two modes (saved view vs native view). It is clear what the tool does, though it never names a sibling to contrast with, so an agent must infer its niche against page_filters or filter_validate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains mechanics but gives no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. An agent cannot tell from this text when to reach for this tool instead of page_filters or filter_validate.

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