Skip to main content
Typed buyer tools are in beta, rolled out per account.

​
Overview

When you ask Murph to do something on the buyer side — discover products, create a campaign, apply a proposal — 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 buyer tools change that. When your account is enrolled, each covered buyer 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.

​
Availability

Enrollment is controlled per account while the feature is in beta. To request it for your account, ask Murph — it can raise the request with the Scope3 team.

Ask Murph

The assistant these tools run behind.