set_project_context
Set or replace compact project context. The encoded API request body is capped at 512KB. Read existing context first, merge still-valid entries, inspect event names with properties or properties_received, and save only durable product truth tied to goals, activation events, event-name glossary entries, or date annotations for major product changes. Use annotations for meaningful landing page, pricing, onboarding, feature, release, or experiment changes; do not store git commit logs, noisy edits, PII, secrets, or long release notes.
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": {
"project": "<project>"
},
"name": "set_project_context"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goals | No | Short business goals, max 5 | |
| project | Yes | Project name or ID | |
| glossary | No | Event-name glossary entries, max 10 | |
| annotations | No | Major date annotations, max 100 | |
| activation_events | No | Event names that define activation, max 8 |