Ezi Home Services

create_order

Create a service order for the authenticated customer. Call calculate_quote first to get the price and recommended durationHours, then call this once the customer agrees.

Input Schema

TableJSON Schema

Name	Required	Description
`edging`	No
`garage`	No
`address`	Yes	Service address.
`comment`	No	Optional notes for the service provider.
`hallway`	No
`hasPets`	No
`windows`	No
`areaRugs`	No
`backyard`	No
`basement`	No
`bedrooms`	No
`category`	Yes	Service category.
`watering`	No
`yardSize`	No
`bathrooms`	No
`engineBay`	No
`overgrown`	No
`staircase`	No
`tireCount`	No
`baseboards`	No
`excessDirt`	No
`iceBuildup`	No
`iceSalting`	No
`livingRoom`	No
`ovenInside`	No
`carsToClear`	No
`clayAndSeal`	No
`kitchenDeep`	No
`lawnCleanup`	No
`leafRemoval`	No
`serviceType`	No	Specific service type.
`vehicleType`	No
`windowPanes`	No
`drivewayType`	No
`fridgeInside`	No
`frontWalkway`	No
`sendQuoteSMS`	No	Send the customer an SMS summary.
`durationHours`	No	Estimated duration in hours (0.5 increments). Use the value from calculate_quote.
`femaleCleaner`	No
`groutCleaning`	No
`scheduledTime`	Yes	ISO 8601 datetime string (e.g. "2025-07-15T10:00:00-04:00"). Always include the timezone offset.
`windowScreens`	No
`gutterCleaning`	No
`kitchenSurface`	No
`petHairRemoval`	No
`spotCleanDoors`	No
`spotCleanWalls`	No
`windrowClearing`	No
`cleaningSupplies`	No
`soffitsAndFascia`	No
`bookIfPaymentOnFile`	No	If true and a payment method is saved, immediately confirms the booking.

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'create a service order' without detailing side effects, authorization needs, error states, or any constraints. This is insufficient for a mutation tool with 51 parameters.

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?

The description is two sentences (21 words), directly stating purpose and prerequisite. It is front-loaded and efficient without any wasted words.

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

Completeness2/5

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

Given 51 parameters, nested address object, and no output schema, the description fails to explain return values, error handling, or configuration nuances. It leaves significant gaps for a tool of this complexity.

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

Parameters2/5

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

Schema description coverage is only 16%, leaving many parameters undocumented. The description only adds value by noting that durationHours should come from calculate_quote. This single tip does not compensate for the overall lack of parameter explanations.

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

Purpose4/5

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

The description clearly states 'Create a service order' with a specific verb and resource. It mentions the authenticated customer context, which narrows scope. However, it doesn't explicitly differentiate from all siblings, though the reference to calculate_quote provides some distinction.

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

Usage Guidelines4/5

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

The description provides explicit sequence guidance: call calculate_quote first, then this tool after customer agreement. This helps the agent understand when to invoke it. It lacks exclusions or alternatives but is clear for the intended use case.

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

All Ezi Home Services 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

A4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: quoting, ordering, job cancellation, job rescheduling, profile retrieval, service availability lookup, scheduled jobs listing, and current datetime. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, such as calculate_quote, cancel_job, get_profile, etc. No mixing of conventions.

Tool Count5/5

8 tools is well-scoped for a home services booking server. It covers the essential customer-facing operations without being too few or excessive.

Completeness4/5

The tool set covers the core workflow: checking services, getting quotes, creating orders, managing jobs (view, cancel, reschedule). Minor gap: no tool to update profile or payment method, but the surface is largely complete for the stated purpose.

Resources

Need Help?