Skip to main content
Glama

Filter Validate

filter_validate
Read-only

Validate predicate and/or filter trees against a datasource to catch configuration errors before applying or saving filters.

Instructions

Validate predicate/and/or filter trees against an attached datasource.

Predicate: kind=predicate, field={name or expression}, condition=GT/T/IN/etc, include=true/false, string_values/number_values. Group: kind=and/or, children. Metric role requires explicit field aggregation; formulas use server validation. No retained chart concept IDs. Matching source draft/published required; blends and parameter filters are not characterized here. Returned concept IDs are provisional. Success validates configuration, not query results or saved state.

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": {
      "datasource_id": "<datasource_id>",
      "tree": "<tree>"
    },
    "name": "filter_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
treeYes
report_idNo
datasource_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true is consistent with 'validate', and the description adds real behavioral context beyond annotations: returned concept IDs are provisional, no chart concept IDs are retained, and success validates configuration rather than query results or saved state. That last clause meaningfully bounds what a passing result proves, which the annotation alone would not convey.

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 opening sentence is front-loaded and earns its place, but the middle is a telegraphic spec dump ('Predicate: kind=predicate, field={name or expression}, condition=GT/T/IN/etc') that restates the JSON schema in prose fragments. Phrases like 'No retained chart concept IDs' are terse to the point of ambiguity.

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 deeply nested schema with an output schema present, this covers the structural rules, the role/aggregation constraint, the draft/published requirement, and the limits of what validation means. Only report_id semantics and the intended use of the returned IDs remain unclear.

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?

With 0% schema description coverage, the description carries the burden and largely does: it explains the predicate/group shapes, the field name-or-expression choice, condition codes (GT/T/IN), include, and the value arrays, plus the metric-role aggregation rule. It leaves report_id unexplained and only implies the datasource attachment, so it does not fully compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Validate') and a precise resource ('predicate/and/or filter trees') plus scope ('against an attached datasource'). The naming of siblings blend_validate and formula_validate as other validators with different resources makes the boundary obvious without extra reading.

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

Usage Guidelines4/5

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

Gives an explicit exclusion set ('blends and parameter filters are not characterized here') and a prerequisite ('Matching source draft/published required'), which steers the agent away from unsupported cases. It does not state a positive 'use this when X, use formula_validate when Y' routing rule, so it stops short of a 5.

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