Well

Get own company

well_get_own_company

Read-only

Get which company the workspace itself is: the confirmed own-company anchor (anchor) and any detected companies not yet confirmed as it (candidates).

Use this whenever a question turns on "mine" versus "theirs" — my payables, my receivables, invoices I owe, what we billed — and then filter by the company_id this returns. Never decide which records are the workspace's own by comparing a company NAME: the same legal entity appears under several labels (a registered name, a trade name, a bank-issued label), so a name filter silently drops rows.

Returns anchor (company_id, registered_name, trade_name) or null when the workspace has not resolved one yet, and candidates (each with company_id, names, role, confidence_score, state).

anchor: null means the workspace has no confirmed own company. Say so plainly and do not promote a candidate to the anchor yourself — a candidate is a detection, not a decision, and confirming one is a user action.

⚠️ TO ASK THE USER WHICH COMPANY on a card so they can pick or search for it, call well_show_company_candidates INSTEAD: it draws a tile per candidate with a registry search and waits for the click. This read draws nothing.

Registry tax ids and registered addresses are deliberately not returned.

Call this directly — no other tool call is needed first. Both the anchor and the candidates are read from the same workspace this call is scoped to.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workspace_id`	No	Target workspace. This read reports one workspace's own data. Omit it and the token's primary workspace answers, which may not be the one you mean; the result names the workspace that did.
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`anchor`	Yes
`success`	Yes
`candidates`	Yes
`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.
`resolved_workspace`	No	The workspace that answered, when the caller named none and the token authorizes several.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id

Added value: +{
+  "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_note

Added value: +{
+  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_source

Added value: +{
+  "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
+  "enum": [
+    "host_meta",
+    "argument",
+    "minted"
+  ],
+  "type": "string"
+}

Changed7 schema fields changedSep 16, 2026

addedOutput schema / properties / candidates / items / properties / business_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The company's legal form (SAS, Inc, GmbH), when known."
+}

addedOutput schema / properties / candidates / items / properties / confirmable

Added value: +{
+  "description": "Whether well_create_company_workspace accepts this candidate now. False for a name-only detected candidate with no groundable identity, or one that has left the surfaced set.",
+  "type": "boolean"
+}

addedOutput schema / properties / candidates / items / properties / confirmable_reason

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "not_open",
+        "not_surfaceable",
+        "not_primary",
+        "already_confirmed",
+        "not_grounded"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Why confirmable is false, null when true. not_grounded: no registry or tax identifier to mint from; ask the user to search the registry and pick the verified entry. not_open: no longer the surfaced candidate; re-read the own-company list before acting. Others: not_primary, already_confirmed, not_surfaceable."
+}

addedOutput schema / properties / candidates / items / properties / country

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The company's country, for a light detail panel."
+}

addedOutput schema / properties / candidates / items / properties / domain

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The company's domain, a logo source and a display fallback."
+}

addedOutput schema / properties / candidates / items / properties / remote_logo_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A resolved logo url when one is known; null otherwise."
+}

changedOutput schema / properties / candidates / items / required

Previous value: -[
-  "candidate_id",
-  "company_id",
-  "registered_name",
-  "trade_name",
-  "role",
-  "state",
-  "confidence_score"
-]New value: +[
+  "candidate_id",
+  "company_id",
+  "registered_name",
+  "trade_name",
+  "role",
+  "state",
+  "confidence_score",
+  "domain",
+  "remote_logo_url",
+  "country",
+  "business_type",
+  "confirmable",
+  "confirmable_reason"
+]

Changed2 schema fields changedSep 15, 2026

addedOutput schema / properties / candidates / items / properties / candidate_id

Added value: +{
+  "description": "The candidate's id — pass to well_create_company_workspace to mint the company workspace from it.",
+  "type": "string"
+}

changedOutput schema / properties / candidates / items / required

Previous value: -[
-  "company_id",
-  "registered_name",
-  "trade_name",
-  "role",
-  "state",
-  "confidence_score"
-]New value: +[
+  "candidate_id",
+  "company_id",
+  "registered_name",
+  "trade_name",
+  "role",
+  "state",
+  "confidence_score"
+]

Changed2 schema fields changedAug 31, 2026

changedInput schema / properties / workspace_id / description

Previous value: -"Target workspace. Omit to use the only authorized workspace, or (for read tools) to query all authorized workspaces grouped by workspace. Required for write tools when the token authorizes more than one workspace."New value: +"Target workspace. This read reports one workspace's own data. Omit it and the token's primary workspace answers, which may not be the one you mean; the result names the workspace that did."

addedOutput schema / properties / resolved_workspace

Added value: +{
+  "additionalProperties": false,
+  "description": "The workspace that answered, when the caller named none and the token authorizes several.",
+  "properties": {
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspace_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "workspace_id",
+    "name"
+  ],
+  "type": "object"
+}

AddedAug 20, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavior beyond that: `anchor: null` means no confirmed own company, candidates must not be promoted to anchor, registry tax ids and addresses are intentionally omitted, and this read draws no UI. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded with the core behavior and each block earns its place: the mine-vs-theirs usage rule, the explicit alternative routing, the null-anchor handling, and the withheld-fields disclosure. The warning callout for `well_show_company_candidates` is particularly well placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with an output schema and safety annotations, the description covers everything an agent needs: what the two outputs mean, how to handle null anchor, what is not returned, and how to route interactive candidate selection to a sibling. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters fully. The description adds scoping context ('read from the same workspace this call is scoped to') but no parameter syntax or format details beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get which company the workspace itself is', and concretely defines the two outputs (`anchor` and `candidates`). It explicitly distinguishes itself from the sibling `well_show_company_candidates`, so an agent can tell them apart without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance ('whenever a question turns on "mine" versus "theirs"'), an explicit anti-pattern (never filter by company NAME), and names the alternative to use instead for interactive selection (`well_show_company_candidates`). It also states no prerequisite call is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?