FieldPulse MCP by usefulapi

Most tools cleanly separate resource and action (list_ vs get_ vs create_/update_), so an agent can usually select correctly. The main confusion is the pair fieldpulse_list_job_status_workflows and fieldpulse_list_job_workflow_statuses, which sound nearly identical and both deal with job statuses, plus some ambiguity between get_item and list_items (invoice item vs catalog).

Every tool uses the same fieldpulse_ prefix followed by a verb_noun snake_case pattern, and the HTTP verb style is consistent throughout. No mixing of camelCase or alternative verb conventions.

43 tools is well above the 25+ threshold and many are thin list/get wrappers around individual endpoints. While the domain is broad, the surface feels endpoint-driven rather than workflow-scoped, making the set heavy for agents to navigate.

The surface is overwhelmingly read-only: create/update exist only for customers and jobs, with no delete operations and no create/update for estimates, invoices, payments, contracts, projects, vendors, purchase orders, items, assets, or locations. Core field-service workflows like issuing an estimate, recording a payment, or managing a purchase order cannot be completed, creating significant dead ends.