Skip to main content
Glama

WritersLogic verifiable AI agents

causalReferee

Causal Claim Referee — Referees a causal claim against an observational table (JSON rows, CSV text, or a published contingency table with counts) and leads with a verdict, confidence, whether the claim holds, the crude and adjusted effects with bootstrap intervals, and a concrete next step. Underneath: crude and stratified effects, Mantel-Haenszel pooling, Simpson's-paradox detection, d-separation and backdoor/front-doo

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": {
      "treatment": "<treatment>",
      "outcome": "<outcome>",
      "covariates": "<covariates>",
      "claim": "<claim>"
    },
    "name": "causalReferee"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNoAlternative to data: CSV text with a header line (comma, semicolon or tab separated; quoted fields allowed; at most 20000 data rows). Numeric cells become numbers.
dagNoYour causal DAG (formal input: no LLM is called to build the graph or, by default, the report). Omit to have one proposed by two independent model samples, which is then an assumption.
binsNoQuantile bins for numeric covariates, default 4.
dataNoObservational table as an array of row objects (at most 20000 rows). Cells are string, number, boolean or null; rows missing a used variable are dropped. Provide this or csv.
seedNoSeed for bootstrap and Monte Carlo; default derived from the input hash.
alphaNoSignificance level for the permutation test and the (1-alpha) bootstrap interval, default 0.05.
claimYesThe causal claim being refereed, in plain language.
outcomeYesBinary column (risk difference, risk ratio, odds ratio) or numeric column (mean difference).
llmReportNoAsk a model to write the executive report in prose (numbers verified in code, template fallback). Default false: the report is a deterministic template over the computed results.
treatmentYesColumn with exactly two distinct values.
covariatesYesCandidate adjustment variables (at most 12). Numeric ones with more than `bins` distinct values are cut at deterministic quantile edges; others must have at most 20 levels.
countColumnNoName of a column holding how many times each row repeats, so a published contingency table can be sent as a few aggregate rows (counts must be non-negative integers; the expanded table is capped at the row limit).
outcomeTypeNoForce the outcome type; inferred from the number of distinct values otherwise.
descriptionsNoOptional one-line description per variable, used only to propose the DAG.
successValueNoOutcome value that counts as success for a binary outcome; same default rule.
treatedValueNoTreatment value that counts as treated; required unless the values are numeric or boolean (then the larger is treated).
bootstrapRepsNo
claimDirectionNoDirection of the claimed effect of treated vs control; default nonzero.
permutationSamplesNoUsed only when the exact enumeration would exceed 1000000 label assignments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources