context-resolution

Resolving Fynd store context

Most Fynd commerce tools operate on a specific company (the seller account) and often a specific application (a storefront/sales channel under that company). Your MCP session is already bound to one organization; within it you still need the right company and application.

Rules

1. Resolve before acting. If a tool needs company_id / application_id and you don't have them, resolve them first — list the available companies/applications with the appropriate tool and pick the match.
2. Single operation → the active/most-recent context. If exactly one company (or application) is in play, use it without asking.
3. Ambiguous or multiple matches → ask the user once, presenting the options (name + id), then proceed with their choice.
4. Named mention → resolve by name. If the user says "for " or "@", match that name to a company/application and use it.
5. Comparison across stores → use all relevant contexts, not just the first.
6. Reuse resolved context for the rest of the conversation unless the user switches stores.

Anti-patterns

• Don't hard-code or guess numeric ids — always resolve them from a listing tool.
• Don't re-ask for context you already resolved this conversation.
• Don't proceed with a write when the target store is ambiguous — confirm first.