Skip to main content
get_monitoring_service_assurance Read supplied-record coverage, freshness and scheduler availability for one project. Unknown evidence and unproved delivery or soak remain explicit.
Development preview. This command is absent from the verified deployed bundle. Use a matching development environment.
This read does not start a verification job.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Reports only supplied project records. Active freshness excludes paused records; last attempt, conclusive check and retained present/absent link verification have separate meanings. A narrow scope sees denied index evidence without counts. Global operator work/customer counts never appear. Optional scheduler timestamps describe invocation metadata only. Soak, backup restoration and actual external delivery remain not_established without their independent acceptance. This read never enrolls a record, changes cadence or starts collection.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • schemaVersion (number, required): must equal 1
  • workspaceId (string, required): Identifier returned by the related operation. minLength: 1; maxLength: 200
  • projectId (string, required): Identifier returned by the related operation. minLength: 1; maxLength: 200
  • asOf (string, required): format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$”
  • source (object, required): additional fields rejected
  • target (object, required): additional fields rejected
  • monitoringProjection (object, optional): additional fields rejected
  • sourceLinkVerification (object, required): additional fields rejected
  • sourceJobs (object, required): additional fields rejected
  • overdueReasons (object, required).
  • index (object / object / object, required).
  • serviceTicks (object, required): additional fields rejected
  • assurance (object, required): additional fields rejected
  • denominator (string, required).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

Follow the related workflow, inspect capability status, or return to the command index.