Record a setup step
record_setup_stepRecord the goal, a note, or a planned setup step. Administrator-only. agent_connected is owned by connection evidence; goal and note complete as recorded narrative, never assertions. Goals require application_id (or an Application goal step_id) and expected_outcome_revision. Project goal writes refuse with setup_requires_application: Setup is per Application; pass application_id. Goal completion requires a 20–2,000 Unicode character Application outcome; omitted or empty summary reuses only that Application outcome, and completion is refused if neither is valid. Accepted same-text CAS increments too and stale retries conflict. Application writes never read or change Project Overview. Plan datasources, solutions, apps and other independently created components. An Application holds one Hosted App. An app plan's subject.ref is accepted under an Application only when that Application can publish it: a published Application's own slug, or a slug no app holds under a draft. Any other is refused, and the refusal says which plan can bind. For a new app with no draft, plan its slug without application_id so the Application its first publication creates adopts it. Do not plan credentials, connector, schema or requests steps: the Project opens them itself once the datasource exists, and a Managed Project Database's requests step only once a Request is suggested against it; describe that work in the datasource step's summary instead. Recording kind ontology or questions with a datasource subject names that datasource's description work: the Project claims the step it already opened and answers with that step_id and state instead of appending a second one. A named ontology step becomes visible and required immediately. A named questions step stays hidden and optional until a human question exists, then becomes required. Connect the datasource first. An existing open observed step may be marked complete or failed, stored as asserted with your actor and summary, without changing component state or granting authority. A requests step cannot be asserted complete: it completes only when live state has no pending Request for its datasource and, except for the Managed Project Database, an approved, enabled Request. A members step cannot be asserted complete: it requires at least one non-Administrator person or invitation and an explicit MCP level decision for every Role holding one. A questions step cannot be asserted complete: it completes only when live state shows no human answer is owed. Every supported observed-kind assertion, complete or failed, requires summary as its reason. Close an unneeded entry that is still planned with state superseded and a summary giving the reason; this retires only that plan, leaves the summary it was authored with, and does not assert component completion or failure. Entries in any other state cannot be superseded here. The one exception is an open requests step. When the recorded goal needs no approved Request for that datasource (for example ad-hoc query access only), close it with state superseded and a summary giving the reason; do not assert it failed. The step is recorded as not needed, changes no Request, and is refused while a Request for that datasource awaits a decision. A later suggested Request opens a new Approve Requests round. A Data Access Point still requires an approved Request. A goal cannot be superseded: goals are recorded, never superseded, because a closed goal cannot be recorded again. Title limit 120 characters; summary limit 2000; at most 200 planned entries. Creation tools bind an explicit setup_step_id, otherwise the same session's oldest unbound plan of that kind matching its subject hint, otherwise a new entry. Planning a members step includes invitation_eligibility, the same note list_users reports including upgrade_url, when seat-taking invitations are restricted; the plan still succeeds. An offer Central did not confirm is not that restriction.
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": {
"kind": "<kind>"
},
"name": "record_setup_step"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | goal and note are recorded narrative. Plan independent components; datasource child steps and requests are opened by the Project. Naming kind ontology or questions claims the description step the Project opened for that datasource. Use an existing step_id to record supported assertions or supersede an unneeded plan. agent_connected belongs to connection evidence. | |
| state | No | Defaults to complete for goal/note, planned for observed kinds; superseded requires an existing planned entry, or an open requests step, and a summary reason | |
| title | No | At most 120 characters | |
| step_id | No | Existing step UUID to update, assert or supersede | |
| subject | No | Subject address: type, id (UUID), ref (provider, solution ID or app slug hint). A planned entry has no bound id. | |
| summary | No | Goal completion requires a 20–2,000 Unicode character Application outcome. Omitted or empty summary reuses only that Application outcome; completion is refused if neither is valid. It is required for every observed-kind assertion and as the reason for superseding a planned entry or declining an open requests step, whose own summary is left as authored | |
| application_id | No | Application UUID, required for a goal unless step_id selects an Application goal; a step_id inherits its persisted Application. A shared step keeps the Application it was opened for; steps this call opens record this one. | |
| parent_step_id | No | Existing parent step UUID | |
| expected_overview | No | Dormant Project goal parameter. Project goals are refused; Application goals use expected_outcome_revision | |
| expected_revision | No | Dormant Project goal parameter. Project goals are refused; Application goals use expected_outcome_revision | |
| expected_outcome_revision | No | Required nonnegative integer for Application goal completion, including same-text writes. Read the current revision with describe_application. |