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

# MCP tools and limits

> Understand the read-only Almanac tools exposed to an AI client.

## Available tools

| Tool                             | What it returns                                 |
| -------------------------------- | ----------------------------------------------- |
| `list_wikis`                     | Wikis available to the signed-in user           |
| `search_wiki`                    | Ranked page results for an explicit wiki handle |
| `read_page` · `list_pages`       | Page content and page summaries                 |
| `list_topics` · `read_topic`     | Topics and their pages                          |
| `source_tree` · `search_sources` | Source-library structure and records            |
| `read_source`                    | One source record by source ID                  |

## Boundaries

MCP is read-only. It cannot:

* create or link wikis
* upload local files
* run ingest or Garden jobs
* manage billing, members, keys, or settings
* infer a wiki from a local project

Use the [CLI](/cli/overview) when an agent has terminal access and needs local
files or write operations. Use the [Python SDK](/sdk/python) or [REST API](/api/overview)
for programmatic writes.

## Prompt with explicit context

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
Search acme/company-handbook for the escalation policy. Read the top result,
then inspect its source records before answering.
```

The explicit handle prevents an agent from reading the wrong wiki. Asking it to
inspect sources makes the evidence requirement clear.