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

# Decision tools

> Ask yes or no questions about companies and people from your AI agent

Two MCP tools let your agent answer yes or no questions about a company or a person, such as
*"Does linfox.com offer cold chain logistics?"* or *"Is this person a founder?"*. They work the same
way as the [Decisions API](https://docs.firmable.com/api-reference/decisions.md).

Both tools are on the Firmable MCP server and the [developer MCP server](https://docs.firmable.com/developer/mcp.md),
from version 0.13.0. You don't need to set anything up: ask your agent a yes or no question and it
uses them.

Every answer is `yes`, `no` or `unknown`. `unknown` means Firmable doesn't hold the fact. It is not a
no.

## make\_decision

Answers a yes or no question. There are two ways to call it.

**Ask in plain English.** Give `ask` and who it's about. Firmable picks the decision tool that fits.

```json theme={null}
{ "ask": "Does this company offer cold chain logistics?", "domain": "linfox.com" }
```

**Run a tool directly.** Give `tool` and its `question` inputs, plus who it's about.
[`list_decision_tools`](#list_decision_tools) shows each tool's inputs and an example.

```json theme={null}
{ "tool": "offers_service", "question": { "service": "cold chain logistics" }, "domain": "linfox.com" }
```

### Inputs

| Input | What it is |
| - | - |
| `ask` | The yes or no question in plain English, up to 2,000 characters. |
| `tool` | A decision tool's name, to run it directly instead of letting Firmable pick. |
| `question` | The tool's own inputs, besides who it's about, as in its `input_schema` and `example`. |
| `company_id` or `domain` | The company the question is about. |
| `person_id`, `linkedin_url` or `work_email` | The person the question is about. |
| `records` | Up to 100 companies or people to ask the same question about, instead of one. Each can have your own `external_id`, returned with its answer. |
| `withReasoning` | `true` to also get the reasoning behind each answer. Costs twice as much. |

### Replies

| Reply | What it means |
| - | - |
| `success: true` | `tool` is the decision tool that ran, and `result` is the answer, as the [Decisions API](https://docs.firmable.com/api-reference/endpoint/decisions-make.md) returns it. A batch has `result.results`. |
| `success: false`, `needs_input: true` | The tool Firmable picked needs more inputs, such as a service to check. The reply has the tool's `input_schema` and `example`. Call again with `tool` and `question`. |
| `success: false`, `needs_tool: true` | No tool clearly answers a question about a person. The reply lists the person tools. Pick one and call again with `tool` and `question`. |
| `success: false` with a `message` | Something else needs fixing, such as a missing company or person, or an input the tool doesn't accept. `message` says what. |

When no tool clearly fits a question about a company, Firmable answers it with
`evaluate_custom_decision`, the general tool for any yes or no question about a company.

## list\_decision\_tools

Lists the decision tools `make_decision` can run. It's free. You don't need it before calling
`make_decision` with `ask`, which picks the tool itself.

| Input | Returns |
| - | - |
| None | Every tool, with its name (`tool`), `description`, who it's `about` (`company`, `person` or both), and its `required_inputs` besides who it's about. |
| `subject: "company"` or `"person"` | Only the tools about companies, or about people. |
| `tool: "<name>"` | That one tool, plus its `input_schema` and an `example` question. |

## Credits

`make_decision` costs the same as the [Decisions API](https://docs.firmable.com/api-reference/decisions.md#pricing):

* **1 credit per 25 yes or no answers**, or **2 per 25** with `withReasoning`.
* `unknown` answers, failed rows and failed calls are free.
* A batch is charged per row.
* Picking the tool from `ask` is free, and so is `list_decision_tools`.

On the Firmable MCP server, answers use your subscription credits, then add-on credits. On the
developer MCP server, they use [developer credits](https://docs.firmable.com/developer/credits.md).

## Try it

Ask your agent:

* *"Use Firmable to check whether linfox.com sells to businesses."*
* *"For each of these domains, does the company offer cold chain logistics?"*
* *"Does the person at this LinkedIn URL work at Firmable? Explain why."*


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