Skip to main content
Glama

Ezi Home Services

by io.github.EziServices
OverviewDiscussionsAdmin

reschedule_job

Request to reschedule one of the authenticated customer's upcoming jobs to a new date and time. If a pro is assigned, they must approve before the job moves. Call lookup_scheduled_jobs first to get the job ID. Get explicit customer confirmation before setting confirmed to true.

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job ID obtained from lookup_scheduled_jobs.
reasonNoShort reason for the reschedule, shown to the assigned pro.
confirmedYesMust be true. Only set after the customer has explicitly confirmed.
newScheduledTimeYesNew local date/time at the job address, without an offset (e.g. "2025-07-15T10:00:00").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / newScheduledTime / description
      Previous value: -"New ISO 8601 datetime string for the rescheduled appointment."New value: +"New local date/time at the job address, without an offset (e.g. \"2025-07-15T10:00:00\")."
  2. Changed1 schema field changed
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Short reason for the reschedule, shown to the assigned pro.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does real work: it discloses that a reschedule may be gated on pro approval and that confirmed must reflect genuine customer consent. It does not cover permissions, reversibility, or what happens if approval is denied, but the core side effect (a request, not an immediate mutation) is made clear.

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 short sentences, front-loaded with purpose and then prerequisites; every sentence adds an actionable constraint with no filler.

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?

No output schema exists, so the description should stand alone, and it covers purpose, prerequisites, and the approval/confirmation gate. It omits the expected response and what happens on a rejected approval, which are minor gaps for an otherwise self-contained definition.

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 coverage is 100%, so all four parameters are already documented in structured form, and the description's parameter content (job ID source, confirmation gating) largely restates it. Baseline 3 applies since the description adds no format or edge-case detail beyond the schema.

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?

Names a specific verb ('reschedule'), the resource ('one of the authenticated customer's upcoming jobs'), and the target fields ('new date and time'). The scope qualifier ('authenticated customer's upcoming jobs') plus the required lookup_scheduled_jobs precursor clearly separates it from siblings like cancel_job or calculate_quote.

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?

Gives an explicit call order ('Call lookup_scheduled_jobs first to get the job ID') and an explicit precondition for the confirmed flag ('Get explicit customer confirmation before setting confirmed to true'). It also states the human-approval gate, so the agent knows the invocation may not take effect immediately.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources