---
name: configure-scope
description: Configures a Tender Town scope so search and triage match what a company sells, where it bids, and what it ignores, then reads the results. Use when the user wants a radar, a scope, better tender or grant results, or to follow a market on Tender Town.
---

# Configure a Tender Town scope

Search with no account stays on the `search` tool. Configuring a scope needs a signed-in account. Follow /mcp.md on this site. Call `get_account` first.

## Learn the need

If the user has not said what they sell, which countries they bid in, and what to ignore, ask. Do not invent a market, a buyer, or a product.

## Choose the scope

Call `list_scopes`.

- Match the need to a catalog scope by the name `list_scopes` returns. Do not invent an id.
- Free cannot create a scope. Turn on one catalog scope with `set_catalog_scope`. General stays available and does not use the slot.
- On a plan with one scope besides General, turning another catalog scope on replaces the catalog pick. Say that, and do it only after the user agrees. Do not turn a custom scope off to free the slot.
- Create a custom scope only when `canCustomize` is true, a catalog scope does not fit, and `used` is below `planScopes` (`null` means unlimited). `create_scope` needs `workspace_id`, a short name, and instructions.
- Catalog scopes and General cannot take new instructions.

## What to write

Scope instructions, on `create_scope` or `update_scope`, say who the scope is for, what they sell, the countries, and what is out. Triage reads them and scores what is out below 50.

Then call `configure_scope_agent` for `search` with plain language. Do not send `search_config`. The platform turns that text into the phrases it runs. Write it so the parse can succeed:

- Name the subject in the words a buyer writes, two to five words. One generic word such as "software" floods the radar.
- Give those words in English and in the languages of the countries the user named. If they named none, cover the EU and EEA.
- Include tenders, grants, and news when they want all three.
- Name what looks similar and is out, so those notices are suppressed.
- Use only the facts the user gave. Do not add industries to get more results.

Then call `configure_scope_agent` for `triage` with the same in and out, in plain language. Do not ask it to change its output format.

Call `list_scope_agents` before switching an agent on. Switch on `tender_evaluation`, `proposal_manager`, or `news_report` only when `included` is true.

## After you save

Saving does not fetch notices. Search runs on the plan's schedule: Free once a day, Starter twice, Pro three times, Teams six times. Say that.

Until the next run, call `search` for what is already in the public index. Quote each Tender Town page, `/tenders/{id}` or `/news/{id}`. Do not invent notices.

When the scope has run, call `list_tenders` and `list_news`. Those are the scored finds for the workspace's active scopes, highest relevance first. `search` is the whole public index and is not filtered to the scope. If the scope list is empty and the scope was just saved, wait for the next run. Do not widen the instructions to fill the gap.