Resources
The policy documents your agent reads before making recommendations or writes.
The server exposes 17 markdown resources under the lancer:// scheme. They encode the policies, defaults, and playbooks the agent must read before making recommendations or writes. The server instructions require the agent to read the relevant resources first; several rules in them are also enforced server-side.
If your client supports MCP resources natively, the agent fetches them directly. If not, the resource_read tool returns the same content by URI, so every client has access.
You normally never touch these yourself. They are listed here so you know what grounds your agent's behavior, and so you can ask the agent to show you any of them ("read lancer://campaigns/recommendation-policy and summarize it").
| URI | What it covers |
|---|---|
lancer://product/overview | What Lancer is and how the pieces fit together. |
lancer://glossary/data-dictionary | Definitions of the fields and metrics used across tools. |
lancer://upwork/bidder-account-model | How Upwork accounts, agencies, and contractors map into Lancer. |
lancer://campaigns/playbook | How to structure and run campaigns. |
lancer://campaigns/recommendation-policy | What campaign recommendations are allowed, and the evidence they require. |
lancer://campaigns/filter-recommendations | Rules for proposing filter changes. |
lancer://campaigns/search-query-authoring | How to write search queries, including deprecated operators. |
lancer://campaigns/integrations | Webhooks, API keys, notification channels, and external mode. |
lancer://campaigns/diagnostics | How to diagnose an underperforming campaign. |
lancer://examples/campaign-recommendations | Worked examples of good and bad recommendations. |
lancer://proposals/construction | How the production proposal agent assembles a proposal, required reading before touching templates. |
lancer://knowledge-base/overview | What the knowledge base is and how the suitability AI uses it. |
lancer://knowledge-base/structure-guide | How each knowledge base field should be written. |
lancer://knowledge-base/iteration-playbook | How to improve a knowledge base based on results. |
lancer://knowledge-base/suitability-tuning-playbook | The large-scale benchmark-and-tune loop, also delivered by the tune_suitability prompt. |
lancer://onboarding/setup-playbook | The end-to-end first-time setup flow, also delivered by the set_up_lancer prompt. |
lancer://inbox/overview | How inbox and pipeline tools fit together, and the rules for inbox writes. |