Updateverificationperiod
updateVerificationPeriodUpdate a verification period by its CID. This replaces the period in full, so optional fields that are left out are cleared; call retrieveVerificationPeriod first and send the complete definition. Changing the scope is destructive: widening it adds PENDING entries, and narrowing it deletes the entries for removed entities, including answers already recorded.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name | |
| scope | Yes | Which entities a verification period covers. An empty scope covers every entity. Combined conditions all have to hold. | |
| context | Yes | Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your *overall objective* and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information. | |
| endDate | Yes | The day the period closes, inclusive | |
| periodCid | Yes | The CID of the verification period | |
| startDate | Yes | The day the period opens, inclusive | |
| session_id | Yes | Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value. | |
| description | No | What owners are being asked to confirm | |
| requiredRoles | Yes | Cortex roles a user must hold to verify. Empty means any owner of the entity may verify. | |
| reasonRequired | No | Whether a reason is required to mark an entity incorrect. Marking an entity correct never requires one. Defaults to false. | |
| requiredTeamRoleTags | Yes | Tags of team roles a user must hold on a team that owns the entity in order to verify | |
| requiredCustomRoleTags | Yes | Tags of custom Cortex roles a user must hold to verify |