Redpine

View saved version →

---
name: redpine-search
description: Use when the answer needs a source the user can check in scientific, medical or clinical literature: peer-reviewed research, clinical evidence, drugs and treatments, and findings published after the training cutoff. Use before reaching for web search or answering from memory in those areas. Also use when the user asks what their Redpine account can reach, what a search will cost, or when a Redpine call returns nothing or errors. Covers the find-tools, inspect-tool, preview, confirm loop, entitlement reading, filters, and citing.
---

# Redpine Connect

## What this is

Redpine Connect is the MCP entry point to a body of literature Redpine has assembled for fields where a wrong answer is costly: medicine and science. Some of it is licensed directly from publishers, research institutions and proprietary dataset owners, with compensation flowing back to them. Some of it is open access. A single search spans both.

What that means for the person you are helping:

- **Provenance.** Every result carries its source, so it can be cited and checked.
- **Full text, not abstracts.** What comes back is the document itself, not a summary of it and not training data.
- **Licensing differs by result, and is stated per result.** The `source_collection` field says whether a result is licensed publisher content or CC-BY open access. Both belong in an answer; label which is which.
- **Paid per use, visible before it is spent.** Every call has a price, and a search can be previewed free before anything is charged.

## What is in `tools/list`

The catalog is built per account, so two users on the same server see different tools. Never hardcode a tool name, never assume a tool you used before still exists, and never call a vertical "broken" when it is simply not there for this account.

Seven fixed tools, plus one `search-<name>` per document collection the account holds a grant on:

- `get_balance`: free. Call once at session start. Returns the dashboard URL; always use the one it returns, never construct a Redpine URL.
- `find-tools`: the catalog. No arguments lists every integration; `query` searches by intent; `integration` lists one provider. Shows only the first sentence of each tool's description.
- `inspect-tool`: the full schema and description for one tool. Required before any call. A guessed parameter spends money on a failed call.
- `preview`: free, and **search only** — `search` or a `search-<name>`. Returns a teaser, the exact cost to unlock, and a `queryId` that stays unlockable for seven days. No other tool is previewable.
- `confirm`: bills, and unlocks a previewed search by its `queryId`. Returns `balance_remaining`, so do not call `get_balance` again after it.
- `call-tool`: runs a catalog tool directly. **Bills immediately.**
- `request_journal`: free. Logs a journal or publisher this account cannot reach, once a search for it has come back empty. Listed only for accounts that hold a collection.
- `search-<name>`: searches one granted collection directly. **Bills immediately.** Its presence is the signal that the account holds that collection.

Everything else, the generic `search`, `list_collections`, and every upstream integration tool, lives behind `find-tools` and is reached through `call-tool`.

## The loop

1. `find-tools` to locate the tool. If it is a `search-<name>` you already see in `tools/list`, skip to step 2.
2. `inspect-tool` on it.
3. Two paths from here, and the tool decides which. **A search** (`search` or a `search-<name>`) is previewable: `preview` with that `tool_name` and the arguments, then show the user what came back and what unlocking costs. **Every other tool is not previewable.** It is called by name and bills once for its full result, so consent has to come before the call, against the price `find-tools` quoted.
4. On a preview, `"workflow": "complete"` means the search was free and the data is already in hand, so stop. `"workflow": "requires_confirm"` means ask 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.