Dedicated tool guide
mcp_health
Check the authenticated MCP session, setup state, and advertised capabilities before starting a workflow.
Generated contract: apiVersion v1, schemaRevision 2. Examples use placeholders and do not call production.
mcp_health
read-onlyscope: noneHealth/echo probe - verifies the partner token and the chain end to end, and reports under setup which prerequisites for a real send are already met (sender profile, data processing agreement, balance, sandbox, approval) and what the next step is. With checkRender: true it additionally checks whether rendering currently works at all (preview, thumbnail). Call it before building a template you will need to look at.
Input contract
| Field | Type | Requirement | Meaning |
|---|---|---|---|
checkRender | boolean | optional | Additionally probes the render path (composer + rasterizer). Defaults to false. |
Contract-shaped example
mcp_health({ "checkRender": true })A failed or absent capability is a stop condition. The setup step keyed sandbox reports a per-account grant that is off by default; when it is unavailable, rehearse with dryRun: true instead. Never reinterpret a failed capability check as permission to send live mail.
For conditional fields and nested object limits, the generated complete tool reference remains authoritative. See errors and safe agent onboarding before implementing retries or a live send.
Trust and live status
Machine-readable service facts and the current operational status of the partner interface are publicly available at all times, no login needed.