Susman Insurance Agency quote requests

The three tools map cleanly onto a linear workflow: list forms, fetch one form's questions, submit answers. Each targets a distinct resource/action pair (catalog listing vs. form schema vs. submission) with no plausible overlap, and the descriptions reinforce the boundaries by referencing each other's outputs.

All names follow the same verb_noun snake_case pattern (list_quote_forms, get_form_questions, submit_quote_request), with consistent verb choice matching the action type (list for collections, get for a single resource, submit for a write).

Three tools is minimal but each is necessary for the quote-request flow, with no redundancy or filler. It sits at the low edge of the ideal range, which is defensible for a narrow, read-then-submit domain.

Discovery (list), schema retrieval with conditional/repeating-section details (get questions), and submission with validation feedback form a complete end-to-end surface for requesting an insurance quote. Minor gaps exist around post-submission visibility (no way to check a request's status), but the core lifecycle is covered.