Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

Propensity-score matching with balance diagnostics

predictive-analytics_propensity-score-match
Read-onlyIdempotent

Fit logistic propensity scores, match treated to controls 1:1 on the logit within a caliper, and report SMD balance and common-support counts. Price $0.04 USDC. POST /api/v1/predictive-analytics/propensity-score-match. An unpaid call returns the x402 payment terms and does not run.

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": {
      "units": "<units>"
    },
    "name": "predictive-analytics_propensity-score-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoseed, integer, from -9007199254740991 to 9007199254740991. Required.
orderNoorder, string, one of descending_score, ascending_score, random. Required.descending_score
unitsYesunits, array. Required.
replacementNoreplacement, boolean. Required.
caliperSdLogitNocaliperSdLogit, number. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. Object.
pairsNopairs. Array.
balanceNobalance. Array.
caliperNocaliper. Number.
sourcesNosources. Array.
limitationsNolimitations. Array.
commonSupportNocommonSupport. Object.
unmatchedTreatedNounmatchedTreated. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantial behavior: a $0.04 USDC price, the x402 payment handshake, and — critically — that an unpaid call only returns payment terms and does not execute. It also pins down the matching procedure (1:1, logit scale, caliper) so the agent knows what computation will be run.

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?

The methodological purpose is front-loaded in the first sentence, followed by pricing, endpoint, and payment-failure behavior. Every sentence carries new information, though the raw POST path is arguably filler given the tool name already implies the endpoint.

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, so return values need not be spelled out, and the description still previews what is reported (SMD balance, common-support counts). Payment flow and failure mode are explicit. The only gaps are behavioral edge cases such as what happens with unmatched treated units or how replacement interacts with the 1:1 constraint.

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 100%, so the structured fields already carry the parameter documentation. The description adds only marginal semantic value — that the caliper is applied on the logit scale — while leaving replacement, seed, order, and the covariates object unelaborated. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names a specific verb chain and resource: fit logistic propensity scores, 1:1 match treated to controls on the logit within a caliper, and report SMD balance and common-support counts. No sibling in the catalog performs propensity-score matching, so the tool is trivially distinguishable from changepoint-detect, pca, cox-regression, etc.

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 by the methodological phrasing (caliper matching, SMD diagnostics), and the payment precondition is stated. However, there is no explicit when-to-use or when-not guidance, and no named alternative for related tasks such as regression adjustment (cox-regression) or cohort analysis (cohort-retention).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources