> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Typed Storefront Tools
> Give Murph the exact request shape of every storefront operation before it acts
Typed storefront tools are in beta, rolled out per account.
## Overview
When you ask [Murph](/v2/setup/ask-murph) to operate your storefront — set selling
terms, author a product, update operating instructions — Murph translates your
request into an API call. By default it does this through a single general-purpose
tool and reasons out the request shape as it goes.
**Typed storefront tools** change that. When your storefront is enrolled, each
covered storefront operation is presented to Murph as its *own* tool, carrying that
operation's exact request schema. Murph sees the precise fields an operation
expects **before** it makes the call, instead of inferring them.
## What it changes for you
* **Fewer failed operations.** Most tool-call errors come from the assistant
guessing a field name or type. When the schema is attached to the tool, that
class of error largely disappears — the request is shaped correctly the first
time.
* **Same conversation.** Nothing changes in how you talk to Murph. You ask for the
same things in the same way; the reliability improvement happens underneath.
* **Full coverage preserved.** Operations that don't yet have a typed tool still
work through the general-purpose path, so nothing you could do before stops
working.
The storefront tool surface is larger than the buyer one, so it's rolled out on its
own schedule — separately from [typed buyer tools](/v2/features/buyer-typed-tools).
## Availability
Enrollment is controlled per account while the feature is in beta. To request it
for your storefront, ask [Murph](/v2/setup/ask-murph) — it can raise the request
with the Scope3 team.
## Related
The assistant these tools run behind.
One of the storefront operations Murph runs for you.