> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-mcp/tool-reference.md).

# Tool reference

Find the tool for the resource you want to inspect, change, or run. Each entry includes typed inputs, an example call, a result excerpt, and the behavior to check before continuing.

MCP examples contain **tool arguments**, not REST request bodies. Replace bracketed IDs with IDs returned from your account. For project inputs and evaluation contracts, use the project's actual input and output keys.

| Resource                                                                                                   | Typical tasks                                                                  |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| [Connection and organization](/stackai-mcp/tool-reference/connection-and-organization.md)                  | Check capabilities, identify your account, and select an organization.         |
| [Projects and workflow authoring](/stackai-mcp/tool-reference/projects-and-workflow-authoring.md)          | Inspect, create, edit, validate, import, or run a workflow.                    |
| [Connections, knowledge and discovery](/stackai-mcp/tool-reference/connections-knowledge-and-discovery.md) | Find authorized connections, available actions, triggers, and source evidence. |
| [Runs and audit logs](/stackai-mcp/tool-reference/runs-and-audit-logs.md)                                  | Diagnose workflow execution or inspect organization activity.                  |
| [Evaluations and monitoring](/stackai-mcp/tool-reference/evaluations-and-monitoring.md)                    | Define test cases, score outputs, compare results, and monitor live runs.      |
| [Skills and versions](/stackai-mcp/tool-reference/skills-and-versions.md)                                  | Manage reusable instructions and review or restore their versions.             |
| [File uploads](/stackai-mcp/tool-reference/file-uploads.md)                                                | Upload a file before passing its URL into a workflow.                          |

## Before your first call

Use `server_info` to check connection capabilities and `whoami` to confirm your organization. Discovery tools return the IDs needed by later calls. Follow pagination whenever a result has more pages.

For a guided sequence, choose a [workflow recipe](/stackai-mcp/workflow-recipes.md). For a plain-language task, choose a [starter prompt](/stackai-mcp/starter-prompts.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-mcp/tool-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.