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

# Finding tools

> How your agent discovers and calls every Fincept tool without loading the whole catalog.

Fincept MCP has hundreds of tools. Listing all of them would fill your agent's context before it starts, so the server lists a **core set** and three discovery tools. Every other tool stays callable by name.

## What is listed by default

* **Core tools**: the most used tool of each area, for example `market_get_quote`, `market_get_candles`, `data_search_series`, `stats_ols`, `stats_arima`.
* **Discovery tools**: `fincept_search_tools`, `fincept_describe_tool`, `fincept_call_tool`.
* **Engine catalogs**: `stats_catalog`, `forecast_catalog`, `alloc_catalog`, `pfopt_catalog` and `quant_catalog` list each engine's modules and tools.
* **`fincept_read_result`**: pages through large results. See [results](/guides/results).

## How the agent finds the rest

<Steps>
  <Step title="Search">
    `fincept_search_tools` takes plain words and returns matching tools with their signature and what they do.

    ```json theme={"dark"}
    { "query": "option chain greeks", "limit": 5 }
    ```
  </Step>

  <Step title="Describe">
    `fincept_describe_tool` returns one tool's full description and JSON input schema.

    ```json theme={"dark"}
    { "name": "market_get_options_chain" }
    ```
  </Step>

  <Step title="Call">
    The agent calls the tool by name, exactly like a listed tool. Clients that only call listed tools can use `fincept_call_tool`:

    ```json theme={"dark"}
    { "name": "market_get_options_chain", "arguments": { "symbol": "AAPL" } }
    ```
  </Step>
</Steps>

<Tip>
  Agents follow this pattern on their own; the server's instructions tell them to. Naming the area in your prompt ("using Fincept's filings tools...") speeds it up.
</Tip>

## List whole toolsets

Add `toolsets` to the endpoint URL to list more tools up front. Use `all` for everything, or a comma-separated list:

```text theme={"dark"}
https://enterprise.fincept.in/mcp?toolsets=market,data,stats_tsa_models
```

| Value | Listed |
| - | - |
| *(none)* | Core tools and discovery tools |
| `market,data` | Core tools plus every tool in `market` and `data` |
| `all` | Every tool |

Unknown names are ignored. Platform toolset names are in the [toolsets reference](/reference/toolsets/overview). Engine toolsets are named `<prefix>_<module>`, such as `stats_tsa_models`, `forecast_backtest` or `alloc_parity`, and listed in each engine's reference: [Fincept Stats](/reference/stats/overview), [Fincept Forecast](/reference/forecast/overview), [Fincept Allocation](/reference/allocation/overview), [Fincept Portfolio Optimizer](/reference/portfolio-optimizer/overview) and [Fincept Quant](/reference/quant/overview).

<Warning>
  `all` lists several hundred tools. Many clients cap or slow down with that many; prefer a short list of the toolsets you use.
</Warning>

## Tool annotations

Each tool declares MCP annotations your client can use for approvals:

| Annotation | Meaning |
| - | - |
| `readOnlyHint: true` | Reads data only. Most tools. |
| `destructiveHint: true` | Deletes or overwrites something in your account. |
| `idempotentHint` | Repeating the call with the same arguments has no further effect. |

Tools that write to your account (saving a watchlist item, placing a paper order) say so in their description and annotations.


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