Skip to main content
Glama
jobber-mcp
by chrischall

List scheduled visits

jobber_list_appointments
Read-onlyIdempotent

List scheduled visits from a Jobber Client Hub grouped as Today, Upcoming, or Past, with optional date-range filtering and brief or full output.

Instructions

Scheduled visits from a provider's Jobber Client Hub, grouped Today / Upcoming / Past. Each visit carries date, weekday, time, arrival window, location and confirmation state. time is null when the provider chooses not to show times. start/end keep only visits dated in that inclusive range. Read-only.

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": "jobber_list_appointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLatest visit date to include, YYYY-MM-DD (inclusive).
hubNoWhich provider hub to read, by label. Omit when only one is configured.
viewNo"full" (default) returns the records; "brief" returns one line per visit: title — <ISO date or "no date"> — <today|upcoming|past>[, confirmed].
startNoEarliest visit date to include, YYYY-MM-DD (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.1
    • addedInput schema / properties / end
      Added value: +{
      +  "description": "Latest visit date to include, YYYY-MM-DD (inclusive).",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / hub / enum
      Added value: +[
      +  "default"
      +]
    • addedInput schema / properties / start
      Added value: +{
      +  "description": "Earliest visit date to include, YYYY-MM-DD (inclusive).",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the records; \"brief\" returns one line per visit: title — <ISO date or \"no date\"> — <today|upcoming|past>[, confirmed].",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered and 'Read-only.' adds nothing. The description does add genuine behavior beyond that: the Today/Upcoming/Past grouping, the field set carried per visit, and the quirk that `time` is null when a provider hides times.

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?

Front-loaded with the resource and grouping, then the per-visit fields, the null-time caveat, and the range filter — four tight, information-dense sentences. Only the trailing 'Read-only.' is dead weight because the annotations already say it.

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 no output schema, the description carries the return-shape burden and mostly meets it: grouping, per-record fields, and the brief-vs-full distinction (delegated to the schema). It stops short of stating result limits, ordering within groups, or unchanged behavior when both date bounds are omitted.

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 start, end, hub and view, including the inclusive-range semantics and the brief/full output formats. The description's '`start`/`end` keep only visits dated in that inclusive range' largely restates the schema and it says nothing about the hub parameter, 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 resource and scope: 'Scheduled visits from a provider's Jobber Client Hub, grouped Today / Upcoming / Past.' The resource (visits) is clearly distinct from the sibling list tools (invoices, quotes, work requests), so an agent can route correctly without opening any 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?

Usage is only implied by the resource name; there is no explicit when-to-use, when-not, or pointer to alternatives such as jobber_read_page or jobber_list_hubs for other data. The 'start'/'end' filtering note hints at one use case but does not frame it against alternatives.

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