Skip to main content
Glama

Analyze event impact

analyze_event_impact
Read-onlyIdempotent

Estimate how a health metric changes before and after a discrete event. Splits data into before/after groups, reports descriptive statistics, and calculates the difference in means with a Welch t-test.

Instructions

Estimate a signal's before/after change around a discrete event.

Splits one signal at an anchor date (e.g. a medication start, procedure, or regimen change) into 'before' and 'after' groups, reports descriptive stats for each, and adds the difference in means plus a Welch t-test.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesthe signal name, e.g. 'resting_heart_rate' or 'a1c_percent'.
userNowhich person; defaults to the primary user.
sourceNo'metric' | 'wearable' | 'lab' | 'biomarker' | 'substance'.metric
event_dateYesthe anchor date (ISO8601 or 'YYYY-MM-DD').
event_labelNooptional description of the event, echoed in the response.
window_daysNoif set, only include readings within this many days on each side of the event; omit to use all available history.
washout_daysNoexclude readings within this many days of the event on both sides (a washout gap) to skip transition-period noise.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context by detailing the statistical analysis (descriptive stats, difference in means, Welch t-test), which is not present in annotations. No contradictions.

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?

Description is concise (2 sentences) and front-loaded with the core verb and resource. It wastes no words, though a bulleted list of outputs could improve scannability.

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?

Given the presence of an output schema (context indicates true), the description appropriately omits return value details. It fully covers the tool's purpose and behavior for an event impact analysis tool.

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?

Input schema has 100% description coverage for all 7 parameters. The description adds high-level meaning but does not enhance understanding beyond what the schema already provides. Baseline of 3 due to high schema coverage.

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?

Description uses specific verbs ('estimate', 'splits', 'reports', 'adds') and identifies the resource ('signal' with before/after change around discrete event). It clearly distinguishes from sibling tools like analyze_trend which focus on continuous trends rather than event-based segmentation.

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?

The description provides clear context for use (e.g., 'medication start, procedure, or regimen change') but does not explicitly state when not to use this tool or name alternatives. It implies usage for discrete events but lacks exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cole-Will-I-Am/HealthLedger-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server