Get workspace graph
well_get_graphDraw the workspace's context graph — its companies, people, accounts, transactions and connectors, and the connections between them — as an interactive canvas the user can orbit, zoom and hover.
Use it when someone asks to see how their business data connects, wants a picture of the workspace, or asks what a company or person is linked to. Narrow the drawing with perspective ("contacts", "money", "accounting"), time_window, min_degree (thin a dense workspace to its hubs) and company_cap.
The card renders the graph itself. This tool's text result reports only the counts, so say what the shape shows rather than listing nodes. When at_company_cap is true the drawing holds as many companies as the cap allows and the workspace may hold more — say the view is capped rather than describing it as the whole graph. When at_email_thread_cap is true the drawing shows each workspace's newest email threads only and older threads are left out.
This tool reads only — it changes nothing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| min_degree | No | Drop nodes with fewer than this many connections. Raise it to thin a dense workspace down to its hubs; 0 keeps every node. | |
| company_cap | No | Cap the number of company nodes drawn. Omit for the server's unbounded default. | |
| perspective | No | Which slice of the graph to draw. "all" is everything; "contacts" is people and companies; "money" is transactions and accounts; "accounting" is the ledger side. Defaults to the server's own default when omitted. | |
| time_window | No | How far back to reach for the underlying records. Defaults to the server's own default when omitted. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| success | Yes | ||
| edge_count | No | Connections between the shipped nodes. | |
| node_count | No | Nodes the server actually shipped, after every filter. | |
| company_cap | No | The company cap the server applied, when one was. | |
| failed_count | No | Open work that cannot progress on its own: stuck tasks and errored connectors. | |
| at_company_cap | No | True when the drawing holds as many company nodes as the cap allowed, so the workspace may hold companies it does not show. It is not a count of what was left out — the projection carries no dropped-row signal. | |
| own_company_id | No | The workspace's own company node, when one is resolved. | |
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| processing_count | No | Open work that may still change the scene: queued or running tasks, plus connectors mid-sync. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| at_email_thread_cap | No | True when older email threads were left out because a workspace held more than the per-workspace email thread cap. The drawing shows each workspace's newest threads only. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |