Propose Profile Mutation
propose_profile_mutationPropose a change to one profile field for later review; the active profile is never changed.
Stores value as a new memory in the proposals bucket at path 'profile.{field}' with metadata status 'proposed'.
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": {
"field": "<field>",
"value": "<value>"
},
"name": "propose_profile_mutation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| field | Yes | Profile field name; the proposal is stored at path profile.<field>. | |
| scope | No | Optional scope that narrows memory access; leave blank for the token default. | |
| value | Yes | Proposed new value, stored as the proposal's content. | |
| team_id | No | Optional team/workspace identifier for team-scoped memory access. | |
| agent_id | No | Optional client-supplied agent label for memory attribution. | |
| metadata_json | No | Optional JSON object of extra metadata; status, proposed_by_agent_id, proposal_type and profile_field are set by the server. | {} |
| agent_instance_id | No | Optional stable, non-secret agent instance ID for per-client attribution. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |