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

# What to Ask

> Example prompts for an assistant connected to the Blockworks MCP server, grouped by use case.

Once the server is connected, you talk to your assistant normally, and it decides which Blockworks tools to call. The
prompts below are patterns that work well, grouped by what you are trying to do. Swap in the assets, protocols, and
timeframes you care about.

If you want to know which tool a given prompt is likely to reach for (document search, the tabular pair, or the
timeseries pair), see the [tools reference](/mcp/tools/overview).

## Market data lookups

Point lookups where you want a current number, not a narrative.

```text theme={null}
What is Bitcoin's current price and 24h trading volume?
```

```text theme={null}
Show me the top 10 assets by market cap, with 7-day price change for each.
```

```text theme={null}
What is Solana's fully diluted valuation compared to its circulating market cap?
```

## Protocol and network research

Questions that need context assembled from several data sources.

```text theme={null}
Give me an overview of Uniswap: what it does, who is behind it, and how its
usage has trended over the past year.
```

```text theme={null}
What is Aave's TVL today, and how has it changed over the last 6 months?
```

```text theme={null}
Who invested in Arbitrum, and at what valuations?
```

```text theme={null}
When is the next ARB token unlock, and how large is it relative to
circulating supply?
```

## Screening and comparison

Ask for a set rather than a single fact, and say what to rank on.

```text theme={null}
Compare Ethereum and Solana on daily active addresses, fees, and transaction
counts over the last 90 days. Put it in a table.
```

```text theme={null}
Which layer-1 networks grew fees the most quarter over quarter? Show the top
five with the percentage change.
```

```text theme={null}
List DeFi protocols with more than $1B in TVL, sorted by 30-day TVL change.
```

## Monitoring and news

Catch-up prompts and recurring checks.

```text theme={null}
What are the most important developments for Ethereum in the past week?
Summarize with sources.
```

```text theme={null}
Summarize crypto fundraising activity this month: rounds, sizes, and the most
active investors.
```

```text theme={null}
Build me a Monday morning briefing on my watchlist (BTC, ETH, SOL, and ARB)
covering price action, onchain activity, and any notable news.
```

## Getting better answers

<Tip>
  For complex or multi-part questions, ask several focused questions instead of one loaded one. Single-topic
  requests usually come back with more depth and fewer gaps.
</Tip>

Quantitative questions work best when you state:

* **The metric**: "TVL", "market cap", "24h trading volume", "daily active addresses".
* **The entity**: the asset, protocol, or network by name.
* **The timeframe**: "last 30 days", "YTD", "since the merge".
* **The baseline**, if you are comparing: "vs last month", "vs Ethereum".

A few habits that pay off:

* **Ask for the shape of the output.** "As a table", "as a bulleted summary", "with the raw numbers" all work.
* **Ask what is available first.** "What Blockworks datasets cover DeFi protocols?" makes the assistant read the
  catalog, which tells you what is queryable before you write a more specific prompt.
* **Name concrete dates for time-sensitive questions.** "The week of March 10" retrieves a sharper set of documents
  than "latest".
* **Give research questions time.** Dataset reads come back quickly, but a document search runs an agent over the
  corpus and can take a while; a slow answer is usually still on its way.
* **Ask it to cite what it pulled.** Requesting the source or the underlying figures makes it easy to spot when an
  answer came from the model's own knowledge instead of from Blockworks data.
* **Follow up rather than restart.** The assistant keeps the earlier results in context, so "now break that out by
  chain" is cheaper and more accurate than a fresh, longer prompt.