Admin Substitute

formation.simulate_business

Read-only

12-Month Business Simulator — financial projection engine for Australian trade businesses. Input a trade, state, startup capital, working hours, and scenario (conservative/realistic/optimistic) to get month-by-month projections including: gross revenue, all expense categories, GST collected/owing, income tax estimates, superannuation, net profit, cash balance, and milestone detection (break-even month, capacity ceiling, hire trigger). Uses real Australian 2025-26 tax brackets, 10% GST, 12% super rate, and trade-specific cost profiles. Returns year-end summary with effective hourly rate, total take-home, and ROI on startup capital.

Input Schema

TableJSON Schema

Name	Required	Description
`state`	Yes	Australian state/territory: NSW, VIC, QLD, SA, WA, TAS, NT, ACT. Required.
`trade`	Yes	Trade category: electrical, plumbing, hvac, painting, roofing, landscaping, carpentry, cleaning, general-building. Required.
`scenario`	Yes	Projection scenario. Required.
`hasVehicle`	No	Already has a work vehicle? Reduces vehicle costs.
`weeksPerYear`	Yes	Working weeks per year (typically 46-48). Required.
`hasAccountant`	No	Has an accountant? Adds $200/month accounting cost.
`startupCapital`	Yes	Starting capital in AUD. Required.
`averageJobValue`	No	Override average job value in AUD (otherwise uses trade average).
`monthlyToolCost`	No	Monthly tool replacement/upgrade budget in AUD.
`businessStructure`	Yes	Business structure for tax calculations. Required.
`leadConversionRate`	No	Lead conversion rate 0-100 (default 40%).
`monthlyVehicleCost`	No	Monthly vehicle lease/loan/fuel cost in AUD.
`billableHoursPerWeek`	Yes	Target billable hours per week. Required.
`marketingBudgetMonthly`	No	Monthly marketing budget in AUD (default $300).
`monthlyPersonalExpenses`	Yes	Monthly living expenses they need to cover in AUD. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint=true (safe read) and openWorldHint=false. The description adds valuable behavioral context: it uses real Australian 2025-26 tax brackets, 10% GST, 12% super rate, and trade-specific cost profiles. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph of 4-5 sentences, front-loaded with purpose, and includes all key details without unnecessary words. It earns its place but could be slightly more structured (e.g., bullet points for outputs).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (15 parameters, 8 required) and the existence of an output schema (referenced), the description is comprehensive: it lists output categories, input parameters, and geographical/regulatory context. It provides enough information for an agent to understand what the tool returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds context for some parameters (e.g., 'Reduces vehicle costs' for hasVehicle, 'Override average job value' for averageJobValue) but does not significantly enhance meaning beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a '12-Month Business Simulator' for 'Australian trade businesses'. It lists specific inputs (trade, state, startup capital, etc.) and outputs (gross revenue, expenses, GST, etc.), distinguishing it from sibling formation tools like formation.checklist or formation.recommend_trade, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for financial projections but does not explicitly state when to use this tool vs alternatives. There is no 'when to use' or 'when not to use' guidance, nor mention of related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Admin Substitute tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools have distinct resource+action naming (e.g., leads.create, jobs.list), but some overlap exists in analytics tools (dashboard, detailed, financials) and workflow automations (process_lead vs google_ads_pipeline). Descriptions clarify purposes, so slight confusion is possible but limited.

Naming Consistency5/5

All tools follow a consistent `domain.action` pattern (e.g., leads.create, billing.status). No mixing of camelCase or snake_case. Even complex names like lifecycle.assess or scaling.readiness_score adhere to the convention.

Tool Count1/5

95 tools is far beyond typical well-scoped servers (3-15). While the server aims to cover an entire business management platform, this volume is overwhelming for an agent, making selection and memory difficult.

Completeness5/5

The tool surface is exceptionally comprehensive, covering formation, hiring, compliance, funding, leads, quotes, jobs, invoicing, payments, marketing, analytics, integrations, webhooks, workflows, and more. Almost no obvious gaps in the lifecycle of running a trade business.

Resources

Need Help?