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

# Tool reference

> Four tools for company discovery, company lookup, observation lookup, and account usage.

Start with [MCP connection setup](/mcp-overview). Call `tools/list` to discover the schemas advertised by the
server you are connected to. These tools return the same business data as the HTTP API.

<CardGroup cols={2}>
  <Card title="Search companies" href="/tools/search-companies">
    Find new companies with evidence relevant to what you sell.
  </Card>

  <Card title="Get companies" href="/tools/get-companies">
    Review evidence for companies you already know.
  </Card>

  <Card title="Get observations" href="/tools/get-observations">
    See what was recorded for known domains since a time.
  </Card>

  <Card title="Get usage" href="/tools/get-usage">
    Check limits or collect a background search's results.
  </Card>
</CardGroup>

## Choose by task

| Your task | Tool | Usage |
| - | - | - |
| Find companies matching a need | [search\_companies](/tools/search-companies) | Metered company search |
| Check known IDs or domains | [get\_companies](/tools/get-companies) | Metered dataset lookup |
| See what was recorded for known domains | [get\_observations](/tools/get-observations) | Metered dataset lookup |
| Check allowance or collect results | [get\_usage](/tools/get-usage) | Unmetered read |

Each tool page explains its arguments, examples, limitations, and response handling.
Search and lookup require a request key. Retry an identical operation with the same key;
use a new key when inputs change or you request the next page.

## Former tools

`get_company`, `search_observations`, `get_observation`, `create_usage`, and `diagnostic`
are no longer advertised or callable on this MCP server. Use `get_companies` for known company
retrieval and `search_companies` with `background: true` for deferred discovery. Existing
observation HTTP endpoints and historical usage reads remain available. Refresh your client's
tool catalog after upgrading.

## Handle responses safely

See [Read an MCP response](/mcp-responses) for the message format, a complete error example,
and how to handle pending, completed, and empty searches.

* Read `result.structuredContent`. Text-only clients can parse the equivalent JSON in `result.content`.
* Check `result.isError` and `structuredContent.error.code`; HTTP success alone is not tool success.
* Reuse a request key only for identical retries. A next page uses a new key with unchanged query,
  filters, limit and target (including omission), plus the returned cursor.
* Stop on subscription or capacity errors. Inspect the structured retry guidance when supplied.
* Do not describe partial or empty coverage as proof that no prospect exists.

OAuth, contact enrichment, and automated outreach are not implemented.