Tools and MCPs

CCDV-F · 21 questions

• A permitting app needs Claude to look up parcels reliably. Which tool design fits?
• A 311 client-side tool can create work orders. Which approval pattern fits?
• A transit harness needs live vehicle positions for Claude. Which dispatch pattern fits?
• A water utility exposes Claude tools near plant operations. Which tool-set construction fits?
• A housing case tool cannot find a case ID. Which error signaling fits?
• A court filing tool updates dockets via Claude. Which description quality fits?
• A school roster tool must fetch attendance every turn. Which tool-use configuration fits?
• A parks inspection tool attaches photos to closure notices. Which validation fits?
• A library catalog agent looks up many ISBNs with Claude. Which efficiency pattern fits?
• A county wants GIS parcel tools reused by permitting and assessor Claude apps. Which MCP approach fits?
• A transit MCP server supports Claude Code with route docs and live ETAs. Which MCP design fits?
• A housing IT team shares case APIs across chatbots. Which MCP deployment fits?
• A school-district MCP provides a networked student-info tool gateway. Which transport choice fits?
• A city needs local file edits in Claude Code and shared permit-database access. Which tooling split fits?
• A 311 team needs reusable tone-of-voice standards across Claude surfaces. Which customization fits?
• A court agent needs current docket state for Claude. Which approach fits?
• A water utility needs a one-off plant report inside a single Claude app. Which customization fits?
• A housing consortium wants eligibility services shared by partner cities. Which MCP pattern fits?
• A library needs citation style guidance and live ILS search for Claude. Which matching fits?
• A transit on-call engineers with Claude Code against logs and GTFS. Which combination fits?
• A school district evaluates a new gradebook capability for Claude. Which decision approach fits?