Flag mid-project scope changes and draft a priced change-order reply. Not legal advice.
Scored across 1 tool
With only one tool there is no possibility of misselection between tools. Its purpose (scope flag + price estimate + drafted reply) is clearly stated and self-contained.
The single tool uses a clear verb_noun snake_case name (generate_change_order) that matches the server's domain. There are no competing conventions to conflict with it.
One tool is thin for a server surface, and that tool bundles three distinct operations (scope classification, pricing, reply drafting) that could reasonably be separate. It is defensible as a single deterministic workflow endpoint, but leaves no room for granular use.
The core change-order workflow is covered end-to-end in one call, but there is no way to retrieve or list prior change orders, adjust an estimated price, or re-draft a reply with different parameters. These are notable gaps for a change-order domain.
Flag whether a client request is in scope, out of scope, or unclear, estimate a price, and draft a polite change-order reply. Not legal advice. Reuses ChangeOrder's deterministic keyword classifier (not an LLM).
Inputs: rate (required), scope (required), request (required), rush, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Freelance scope of work, rates, deadlines, and change orders for AI assistants
Find, date and price each change on a project. Link a cloud folder for daily support or a claim.
Turn client requests into a clear scope and a quote with your rates. 20 tools, PDF/Word exports.
Change orders against quotes and work orders: line changes, approval, running contract value.
Add one secure layer between your agents and this server.