Skip to main content
Glama

Schedule Availability Tool

schedule-availability
Read-only

Calculates verified busy jobs and open planning windows for a local business day without scheduling or changing a job. Use to find scheduling availability in the connected business. Returns date, timezone, planning_window, duration_minutes, job_duration_minutes, busy, available_slots, scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "schedule-availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal business date, YYYY-MM-DD; defaults to today.
workday_endNoPlanning window end hour.
technician_idNoOptional same-business technician ID.
workday_startNoPlanning window start hour.
duration_minutesNoRequested appointment length.
job_duration_minutesNoPlanning duration for existing jobs.

Output Schema

NameRequiredDescriptionDefault
busyYesBounded busy records returned by this tool.
dateYesDate used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
timezoneYesTimezone used or returned by this tool.
available_slotsYesBounded available slots records returned by this tool.
planning_windowYesPlanning window metadata; empty collections retain their existing JSON array representation.
duration_minutesYesDuration minutes for the returned result.
job_duration_minutesYesJob duration minutes for the returned result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "available_slots": {
      +      "description": "Bounded available slots records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "busy": {
      +      "description": "Bounded busy records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "date": {
      +      "description": "Date used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "duration_minutes": {
      +      "description": "Duration minutes for the returned result.",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "job_duration_minutes": {
      +      "description": "Job duration minutes for the returned result.",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "planning_window": {
      +      "description": "Planning window metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "description": "Timezone used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "timezone",
      +    "planning_window",
      +    "duration_minutes",
      +    "job_duration_minutes",
      +    "busy",
      +    "available_slots",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces this with 'without scheduling or changing a job' and the 'verified' qualifier on busy jobs, but adds nothing about permission requirements, timezone resolution, or how 'verified' busy time is determined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core behavior and the no-mutation constraint. The trailing enumeration of return fields is largely redundant given an output schema exists, which is the only real waste.

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?

With a full output schema, complete parameter documentation and safety annotations, the description only needs to establish intent and the non-mutating contract, which it does. Minor gaps remain around timezone handling and what 'verified' means for busy time, but nothing blocks a correct invocation.

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 schema already documents defaults and ranges for date, workday_start/end, technician_id, duration_minutes and job_duration_minutes. The description adds no meaning beyond echoing duration_minutes and job_duration_minutes in the return list, so baseline 3 applies.

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?

States a specific verb and resource: 'Calculates verified busy jobs and open planning windows for a local business day'. The clause 'without scheduling or changing a job' cleanly separates it from write siblings like create-job, so an agent can route without opening the schema.

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?

'Use to find scheduling availability in the connected business' is essentially a restatement of the purpose rather than a decision rule. The negative scope ('without scheduling or changing a job') hints that create-job is the write alternative, but no sibling is named and no conditions for choosing this over jobs-today or get-job are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources