Ezi Home Services

reschedule_job

Reschedule one of the authenticated customer's upcoming jobs to a new date and time. Call lookup_scheduled_jobs first to get the job ID. Get explicit customer confirmation before setting confirmed to true.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	The job ID obtained from lookup_scheduled_jobs.
`confirmed`	Yes	Must be true. Only set after the customer has explicitly confirmed.
`newScheduledTime`	Yes	New ISO 8601 datetime string for the rescheduled appointment.

TDQS

A4.7/5.0

Behavior4/5

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

No annotations provided, but description covers authentication context and confirmation prerequisite. Lacks details on side effects or errors, but sufficient for basic usage.

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?

Three concise sentences, each adding essential information: purpose, prerequisite, and condition. No unnecessary words.

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?

Covers core workflow and constraints, but lacks explanation of return values. Adequate for the tool's simplicity and given no output schema.

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

Parameters5/5

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

Schema coverage is 100%, and description adds workflow context for jobId (from lookup) and confirmed (must have explicit confirmation) 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?

Clearly states verb 'Reschedule' and resource 'one of the authenticated customer's upcoming jobs', distinguishing from siblings like cancel_job.

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 instructs to call lookup_scheduled_jobs first and to get customer confirmation before setting confirmed to true, providing clear sequential guidance.

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?