> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salesgraph.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools overview

> Every tool the Antinuous MCP server exposes.

The server exposes the following tools. Command tools return **markdown** in the standard MCP
`content` text-block format. OMS tools also return `structuredContent`: successes are
`{ "result": ... }` and errors are `{ "error": { "code": ... } }`, with the same JSON in their
text block. Tools marked **async** start a background run and return a run id you poll with
[`get_run_status`](/tools/get-run-status).

All published tools below are standard Antinuous service interfaces. No customer-specific custom
tools are published here.

| Tool | Input | Type | Classification | What it does |
| - | - | - | - | - |
| [`research`](/tools/research) | `topic` | sync | Standard | Cited markdown brief on any topic or company, from public data. |
| [`competitors`](/tools/competitors) | `company` | sync | Standard | Sourced list of a company's direct competitors. |
| [`gtm_audit`](/tools/gtm-audit) | `website` | async | Standard | Org-aware GTM audit of a prospect's website. |
| [`org_audit`](/tools/org-audit) | — | async | Standard | Org-aware audit of your own org, from its sales profile. |
| [`get_run_status`](/tools/get-run-status) | `kind`, `id` | sync | Standard | Poll an async run; returns the result once complete. |
| [`list_capabilities`](/tools/list-capabilities) | — | sync | Standard | Which integrations are active for your org. |
| [`help`](/tools/help) | — | sync | Standard | Catalog of available commands. |
| `oms_metadata` | — | sync | Standard | Visible OMS ontology metadata. |
| `oms_search` | `type`, query options | sync | Standard | Searches visible OMS objects. |
| `oms_get` | `type`, `key` | sync | Standard | Gets one visible OMS object. |
| `oms_pivot` | `type`, `key`, `link`, `direction` | sync | Standard | Traverses a visible OMS relationship. |
| `oms_provenance` | `type`, `key` | sync | Standard | Returns visible object provenance. |
| `oms_watch_create` | watch request | sync | Standard | Creates a continuous Account or Opportunity research watch. |
| `oms_watch_list` | pagination options | sync | Standard | Lists manageable research watches. |
| `oms_watch_get` | `id` | sync | Standard | Gets one manageable research watch. |
| `oms_watch_cancel` | `id` | sync | Standard | Cancels one manageable research watch. |
| `oms_request_update_opportunity` | approval request | sync | Standard | Requests a human-approved opportunity update. |
| `oms_request_log_rep_note` | approval request | sync | Standard | Requests a human-approved rep note. |
| `oms_request_draft_followup_email` | approval request | sync | Standard | Requests a human-approved follow-up draft. |

## OMS tools

Use public OMS object keys everywhere. In particular, `oms_watch_create` takes
`target: { type: "Account" | "Opportunity", key: string }`; it does not take an internal primary
key field. Its `frequency` ranges from `1h` through 30 days. `monthlyCostCapMicros` is
`3000` to `100000000` for `lite`, or `10000` to `100000000` for `base`. Source policies allow up
to 25 valid domains per include or exclude list, with no overlap.

## Sync vs. async

**Sync** tools run and return their markdown in a single call. Research and competitor mapping
typically take tens of seconds.

**Async** tools (GTM audit, org audit) kick off a longer pipeline and return immediately with a
run id. Poll [`get_run_status`](/tools/get-run-status) with the right `kind` until the status is
`completed`, at which point it returns the full markdown result. See
[Async runs](/reference/async-runs).

## Org context

Some tools return richer output when integrations are connected to your organization (for
example, a CRM via Monaco). Tools degrade gracefully to public-data-only results when an
integration isn't present. Use [`list_capabilities`](/tools/list-capabilities) to see what's
active.

<Note>
  If your org hasn't completed onboarding (no sales profile yet), audit tools return an
  `Onboarding required` message instead of starting a run. Finish onboarding in the dashboard,
  then retry.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.