Milewise

Most tools target distinct actions (post_job, review_job_proof, get_job_status, estimate_price), but the set contains four similar supply-discovery tools — search_services, list_task_templates, list_operator_profiles, search_operator_capabilities — whose boundaries only become clear after reading detailed descriptions. An agent could plausibly pick the wrong one when looking for what it can buy.

Names follow a clear snake_case verb_noun pattern with predictable prefixes (create_, get_, list_, search_, review_, run_, estimate_) and a uniform milewise. namespace. The only deviation is post_job instead of create_job alongside the create_* family.

17 tools is slightly heavy but each maps to a real marketplace concern (jobs, payments, proofs, subscriptions, policy, sandbox). The count is reasonable for a service with Stripe integration and operator supply.

The surface covers the job lifecycle (post, status, proof review), payment plumbing, subscriptions, supply discovery, policy, and a sandbox flow. Minor gaps remain — no cancel/abandon job, no get_job detail or job listing, no retrieve of a specific operator profile or service detail.