Ezi Home Services

check_availability

Returns bookable start times and date-specific fees for a service at a postal code. Start times are not reserved slots: a provider is matched after booking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postalCode": "<postalCode>",
      "category": "<category>",
      "serviceType": "<serviceType>",
      "date": "<date>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Local date, e.g. "2025-07-15".
`category`	Yes	Service category.
`postalCode`	Yes	Service postal or zip code.
`serviceType`	Yes	Specific service type.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose two important traits: returned start times are not reserved slots, and a provider is matched after booking. It does not cover permission requirements, rate limits, or error/no-availability behavior, but the core side-effect warning is present and useful.

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 tight sentences with the primary outcome front-loaded and the critical caveat immediately after. There is no redundant wording or unnecessary preamble.

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?

For a four-parameter availability-checking tool with no output schema, the description explains the essential return contents (start times and fees) and an important booking constraint. It could be slightly more complete by describing the shape of the returned availability or what happens when no times are available, but the critical context is covered.

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 the input schema already explains all four required parameters, including date, category, postal code, and service type. The description adds little parameter-specific detail beyond saying the result is for a service at a postal code, which is appropriate as a baseline when the schema does the heavy lifting.

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 states a specific verb and outcome: returns bookable start times and date-specific fees for a service at a postal code. That makes the tool understandable without opening the schema. However, it does not explicitly differentiate itself from siblings such as calculate_quote or get_available_services.

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 phrase 'bookable start times' implies this is used before booking, which gives some usage context. But the description does not explicitly say when to use this tool instead of calculate_quote, create_order, or get_available_services, and it provides no exclusions or prerequisites.

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

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

Need Help?