Skip to main content
Glama

Geo Control-Adjusted Lift

bpj_geo_control_adjusted_lift
Read-onlyIdempotent

Scale the test market’s baseline by the control market trend and compare observed conversions with the counterfactual.

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": {
      "testPre": "<testPre>",
      "testPost": "<testPost>",
      "controlPre": "<controlPre>",
      "controlPost": "<controlPost>"
    },
    "name": "bpj_geo_control_adjusted_lift"
  }
}

Input Schema

NameRequiredDescriptionDefault
testPreYes
testPostYes
controlPreYes
controlPostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds some methodological context (a counterfactual built from the control trend) but says nothing about assumptions, edge cases such as zero post-period conversions, or the shape of the result. Adequate but thin beyond the structured hints.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the abstraction level ('baseline', 'counterfactual') packs two concepts into one clause and could be split for faster parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-required-parameter computation with no output schema, so the description should say what comes back (a lift figure? a ratio or percentage? a per-market breakdown?) and what the counterfactual formula assumes. Neither is present, leaving the agent able to call it but not to interpret or verify the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but each property carries a descriptive title ("Test conversions before launch", "Control conversions after launch"), so the four inputs are self-explanatory from the schema. The description's mapping of test/control to baseline versus observed is consistent with, but adds little beyond, those titles.

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 computation: scale the test market's baseline by the control market trend, then compare observed conversions against the counterfactual. That is a real verb+resource description of a geo-lift calculation, not a restatement of the name. It stops short of naming any sibling or scope boundary that would separate it from other lift/value tools.

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?

There is no when-to-use guidance, no stated preconditions (e.g. that test and control periods must be comparable and aligned), and no mention of alternatives such as other lift estimators. The agent must infer applicability entirely from the sentence itself.

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.