FavCRM

create_service_schedule

Create a bookable schedule window for a service, including recurring weekly/daily availability.

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": {
      "serviceId": "<serviceId>",
      "date": "<date>",
      "startTime": "<startTime>",
      "endTime": "<endTime>"
    },
    "name": "create_service_schedule"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Start date or one-off date (YYYY-MM-DD)
`notes`	No	Free-form notes
`endTime`	Yes	HH:MM (24h)
`staffId`	No	Optional companyMembers.id to bind this schedule to staff
`byWeekday`	No	Weekdays for weekly recurrence: 0=Mon, 1=Tue, ... 6=Sun
`serviceId`	Yes	Service ID
`startTime`	Yes	HH:MM (24h)
`recurrence`	No	Default none
`resourceId`	No	Optional resource ID to bind this schedule to a room/resource
`maxCapacity`	No	Max bookings per generated slot
`recurrenceEndDate`	No	YYYY-MM-DD
`recurrenceInterval`	No	Default 1

Output Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The annotations already indicate a non-read-only, destructive-safe create operation. The description adds no context about side effects, such as whether existing schedules are overwritten, whether slots are generated immediately, or permission requirements. It only restates the purpose without disclosing additional behavioral traits.

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?

A single, direct sentence with no extraneous words. It front-loads the core action and object, making the tool's purpose immediately understandable.

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?

The tool has 12 parameters and an output schema, but the rich schema descriptions and annotations offset the brief description. The description lacks usage nuance about recurrence edge cases, but the schema addresses defaults and formats, making it adequate for a create operation.

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?

The input schema provides complete descriptions for all 12 parameters (100% coverage), so the schema carries the semantic load. The description's mention of 'recurring weekly/daily availability' aligns with recurrence fields like recurrence, byWeekday, and recurrenceEndDate, but adds no detail beyond what the schema already documents.

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?

The description clearly identifies the action ('Create'), the target ('a bookable schedule window'), and the scope ('for a service'), distinguishing it from booking tools like create_booking and update operations like update_service_schedule. The phrase 'including recurring weekly/daily availability' adds specificity to the tool's recurring capability.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives such as set_resource_availability or list_service_schedules. The description implies it is for creating service-level schedule windows but does not mention exclusions, prerequisites, or scenarios where another tool should be preferred.

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

All FavCRM 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.