Read-only desk for buyers and assistants: offer, prices, fit check, readiness scan, intake draft.
Scored across 7 tools
Most tools target clearly different outputs: pricing (get_offers/estimate_engagement), method (get_approach), scoping (scope_mapping_session), and a hand-off artifact (prepare_intake_request). The one fuzzy boundary is check_fit vs run_readiness_scan, since both assess a prospect and both can point to a starting point, though their inputs and scoring bases differ. Descriptions mostly resolve this, but an agent could still hesitate over which assessment to run first.
All seven names are snake_case verb_noun formations (check_fit, get_offers, run_readiness_scan, scope_mapping_session, prepare_intake_request). The verb choice is predictable by intent: get_ for retrieval, check_/run_ for assessment, scope_/prepare_ for producing an artifact. No mixed conventions.
Seven tools for a read-only buyer-desk surface is well scoped, and each maps to a distinct stage of the presales conversation (fit, approach, price, scope, readiness, intake). Nothing feels like filler or a duplicate alias.
The set covers the full read-only journey: qualify (check_fit, run_readiness_scan), explain (get_approach, get_offers), price (estimate_engagement), shape (scope_mapping_session) and hand off (prepare_intake_request). Gaps are minor: no way to surface proof/case references or availability/timing, which a buyer desk often needs. As a deliberately read-only surface, it is close to complete.
Deterministic fit check with nine yes/no signals taken from the published article on when an FDE fits and when it does not. Returns one of: fits, start_with_mapping, not_clear_yet, wait, something_else_fits_better, each with the sentence from the site it is based on. It also says when another kind of supplier is the simpler choice. Ask the person; do not guess the signals.
Inputs: signals (required), lang. Returns: next, note, basis, source, +2 more
Adds up the published starting prices for a chosen path of one to three steps (mapping, sprint, fde). Returns the lines, the sum as a lower bound in EUR excl. VAT, what is not included and what is not published. No discounts, no new prices, not a quote.
Inputs: path (required), lang. Returns: vat, lines, notes, source, +6 more
Returns how a forward-deployed engineer of Forwardsmith works: Map, Build, Hand over; the five stations of the method and its golden rule; the six kinds of work; the eight points that belong in a statement of work; what must be ready before the start; and the handover test.
Inputs: lang. Returns: cite, method, ownership, work_types, +4 more
Returns the three ways to start with Forwardsmith (Information Flow Mapping Session, FDE Build Sprint, FDE 30-60-90 engagement) with duration, starting price as a number in EUR excl. VAT, what it delivers, what is not included, the ownership statement and a list of things the site does not publish, so you can say so instead of guessing. Prices are starting prices, not quotes. Please cite the URL.
Inputs: lang. Returns: cite, offers, ownership, price_terms, +2 more
Turns what you learned into a ready-to-send intake request: a brief in ten numbered lines, a link that opens the intake form with the message already filled in, and (once delivery to the inbox is confirmed) an e-mail to contact@forwardsmith.com. It sends nothing and stores nothing: the person reads the text, adds name and work e-mail and sends it. Do not put names, e-mail addresses or phone numbers in any field; the tool refuses them.
Inputs: problem (required), process (required), lang, systems, +8 more. Returns: handoff, brief_id, brief_text, brief_sha256, +2 more
Runs the same six-question FDE Readiness Scan as the page on forwardsmith.com, with the same scoring. Returns the score, the recommended starting point with its starting price, what is already in place and what to prepare. Indicative self-assessment, not a quote.
Inputs: answers (required), lang. Returns: why, offer, answers, same_as, +5 more
Takes one process as 2-20 steps and returns per step whether it is handled by code (MCP/API), by a model (and on which route) or by a person, whether a redaction gate comes first and whether human approval is needed. Fixed rule table from the published method; no model is called. A preview of what the Information Flow Mapping Session does with your team, not a design. Describe steps in general words; no personal data.
Inputs: steps (required), process_name (required), lang. Returns: offer, steps, source, totals, +4 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Public read-only offers, prices, product details, links and safe AI integration guidance.
Agent intake desk for property renovation. Read only, CORS open, fail closed, receipts recompute.
Read-only checks for proposed orders against evidence and policy; no trading or payment authority.
Read-only IT Health Check, domain security, recommendations, pricing, and draft enquiries.
Add one secure layer between your agents and this server.
