Envelope response

A consistent structured reply shape from every tool call: success flag, data, a one-line summary, notable signals, and durable learnings: so an agent always knows what happened and what deserves attention.

LinkedBoost operations use a shared response shape with a success indicator, data, summary, and recommended next steps. Read the status and returned state together. A next-step recommendation is guidance that can require an operator decision, and a successful queue request is not a delivery receipt.

In practice

Check whether a call succeeded, read the returned data and summary, then inspect any recommended next step before acting.

What to check

Recommendations are conditional guidance, not evidence of approval or completion. A successful queued acknowledgment is not a successful send.

Use it in LinkedBoost

get_activity_event
Inspect the recorded payload and outcome of one operation call.
list_agent_activity
Review the workspace's recorded tool calls across MCP, CLI, and HTTP.

Related terms

Model Context Protocol (MCP): The open standard (launched November 2024) that lets AI agents call external systems through typed tools: the USB port between models like Claude and the software that does things.
Queued vs. sent: The distinction dashboards blur: queued means the system plans to send; sent means it actually left. Reporting queued as sent is how tools fake momentum.