Skip to main content
Glama

Formula Validate

formula_validate
Read-only

Validate a calculated-field expression against an attached datasource without saving it, returning Google column metadata or diagnostics for syntax, schema, or connector issues.

Instructions

Validate an expression for an attached datasource without saving any field.

Use internal field references, e.g. ABS(t0.revenue), from datasource_get. Returns Google column metadata (dataType, aggregation/type and semantics) or diagnostics. A validation failure may be syntax, schema or connector failure: inspect diagnostics. Uses native uncached revision-0 validation; isolated unpublished-draft and blend contexts are not yet characterized. Success does not prove business correctness or evaluate resulting values.

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>",
      "expression": "<expression>"
    },
    "name": "formula_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo
expressionYes
datasource_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true: it discloses that validation is native, uncached and revision-0, that failures may be syntax, schema or connector in origin, and that success does not prove business correctness or evaluate values. It is consistent with the read-only annotation ("without saving any field").

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

Conciseness4/5

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

Front-loads the core purpose and keeps to roughly four short sentences with no filler. A few phrases are dense internal jargon ("native uncached revision-0 validation") that cost reading effort without adding agent-actionable detail.

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?

An output schema exists and the description still summarizes the return shape (column metadata vs diagnostics), and the failure-model caveats are unusually thorough. The remaining gap is the unexplained report_id parameter, which matters for correct invocation in report-scoped usage.

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 description coverage is 0%, so the description must carry parameter meaning. It explains the expression format thoroughly and implies datasource_id as the attached datasource, but report_id is never mentioned and its role or optionality is left entirely undocumented.

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 ("Validate an expression") plus a key scope qualifier ("for an attached datasource without saving any field"). That combination lets an agent distinguish a dry-run validator from reference-lookup or write tools, though it never names the closest sibling (formula_references) to sharpen the boundary.

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 concrete input guidance ("Use internal field references, e.g. ABS(t0._revenue_), from datasource_get") and effectively warns against reliance in uncharacterized contexts (isolated unpublished-draft and blend). It stops short of an explicit when-to-use-this-vs-that routing statement, so it is clear context rather than full alternative selection.

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