Admin Substitute

formation.guided_setup

Read-only

RECOMMENDED ENTRY POINT — Intelligent business formation engine. Provide context about the person (trade, state, qualifications, budget, goals) and get a personalised formation plan with: (1) auto-detected pathway (licensed contractor, fresh start, or investor/operator), (2) task list split into AI-actionable vs human-required, (3) direct government portal links, (4) trade-specific insights (common first jobs, suppliers, rates, growth tips), (5) recommended next tool calls, (6) follow-up questions to ask. Call this FIRST, then use the recommended tool chain for deeper dives.

Input Schema

TableJSON Schema

Name	Required	Description
`state`	Yes	Australian state/territory: NSW, VIC, QLD, SA, WA, TAS, NT, ACT
`trade`	Yes	Trade category: plumbing, electrical, hvac, painting, roofing, landscaping, carpentry, cleaning, general-building
`budget`	No	Available startup capital in AUD
`hasABN`	No	Already have an ABN?
`pathway`	No	Override auto-detection: licensed_contractor (already qualified), fresh_start (needs everything), investor_operator (hiring qualified people). Usually omit and let the engine detect.
`hiringPlan`	No	solo, subcontractors, employees, or apprentices
`hasInsurance`	No	Already have business insurance?
`targetRevenue`	No	Annual revenue target in AUD
`yearsExperience`	No	Years of experience in the trade
`businessStructure`	No	Preferred structure: sole_trader, company, partnership, trust, undecided
`isExistingBusiness`	No	Converting from employee to contractor/business owner?
`hasContractorLicence`	No	Do they already hold a contractor licence?
`hasTradeQualification`	No	Does the person have a Certificate III or equivalent trade qualification?

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Describes the input (person context) and output (formation plan with specific sections) in detail. Annotations indicate readOnlyHint=true, which is consistent with the description. No contradictions.

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

Conciseness5/5

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

Single paragraph with front-loaded 'RECOMMENDED ENTRY POINT' and a numbered list of outputs. Every sentence contributes meaning; no wasted words.

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

Completeness5/5

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

Given the tool's complexity (13 params, output schema), the description covers purpose, usage, and outputs comprehensively. It explains what the plan contains, including follow-up questions and recommended next steps, making it self-contained.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by summarizing key parameter groups (trade, state, qualifications, budget, goals) and hinting at usage context, but does not detail each of the 13 parameters individually.

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?

Description clearly states it is an intelligent business formation engine that produces a personalised plan with six specific components. It distinguishes itself from sibling tools by being the recommended entry point.

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

Usage Guidelines5/5

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

Explicitly says 'RECOMMENDED ENTRY POINT' and 'Call this FIRST, then use the recommended tool chain for deeper dives', providing clear when-to-use and sequential guidance.

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?