Skip to main content
Glama
Sign In
juggle-mcp

juggle-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List your Juggle bookings (sits/jobs)

juggle_list_bookings
Read-only

Lists your posted babysitting and petsitting bookings with status, service, start time, booked sitter, and pending application counts; filter by active, past, all, or exact statuses.

Instructions

List your Juggle babysitting / petsitting bookings (the sits or jobs you posted): status (open, booked, in progress, awaiting payment/review, completed, canceled…), service, start date/time, the booked sitter, and how many sitter applications are waiting. status "active" (default) = still in play, "past" = completed/canceled/declined/expired/archived, "all"; or pass exact statuses. Sorted by start time. Use juggle_get_booking for applicants and details.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands; "raw" returns the upstream payload unprojected. compact: id, status (+label), service, start, sitter name, pending applications, recurring series. "full" returns the matching upstream booking items plus the status/service label maps; "raw" the whole page data with the list filtered. A brief title is the service and the booked sitter; its status is the booking status plus any waiting applications. "brief": one line per item, `title — <ISO date or "no date"> — <status>`, at most 120 chars each, in the untrusted-data envelope; a line starting "-- " is a note (`-- N of M shown`, `-- none`).
limitNoHow many bookings to return (default 50, max 200).
orderNoBy start time: "asc" soonest/oldest first (default) or "desc".
offsetNoHow many bookings to skip (default 0).
statusNoWhich bookings: "active" (default), "past" or "all". Ignored when statuses is given.
serviceNoOnly this service.
statusesNoExact booking statuses to include (overrides status).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands; \"raw\" returns the upstream payload unprojected. compact: id, status (+label), service, start, sitter name, pending applications, recurring series. \"full\" returns the matching upstream booking items plus the status/service label maps; \"raw\" the whole page data with the list filtered."New value: +"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands; \"raw\" returns the upstream payload unprojected. compact: id, status (+label), service, start, sitter name, pending applications, recurring series. \"full\" returns the matching upstream booking items plus the status/service label maps; \"raw\" the whole page data with the list filtered. A brief title is the service and the booked sitter; its status is the booking status plus any waiting applications. \"brief\": one line per item, `title — <ISO date or \"no date\"> — <status>`, at most 120 chars each, in the untrusted-data envelope; a line starting \"-- \" is a note (`-- N of M shown`, `-- none`)."
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "compact",
-  "full",
-  "raw"
-]New value: +[
+  "compact",
+  "full",
+  "raw",
+  "brief"
+]
  2. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds useful behavior beyond that — result ordering by start time, the default status window, and the exact fields each booking carries (status, service, start, sitter, pending applications). It stops short of describing pagination interplay (limit/offset with sorting) or any rate/size caveats.

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?

Purpose and scope are front-loaded in the first clause, followed by return fields, then filter semantics, then the sibling pointer — a sensible order. The parenthetical field list and the status enumeration make some sentences dense and run-on, costing a little readability.

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 seven optional parameters, no output schema, and four enums, the description does the needed work: it names the returned fields, defaults, and sort order, substituting for the missing output schema. Minor gaps remain around paging behavior and how limit/offset interact with sorting.

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 every parameter is already documented, which sets the baseline at 3. The description does add meaning by spelling out which underlying statuses collapse into "past" and that exact statuses can be passed instead, but it does not touch view, limit, offset, service, or order beyond what the schema says.

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 — 'List your Juggle babysitting / petsitting bookings (the sits or jobs you posted)' — and immediately clarifies the ownership scope (bookings the caller posted, not ones they applied to). It also enumerates the fields returned, so an agent can distinguish it from juggle_get_booking without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes detail/applicant lookups to juggle_get_booking, and explains the practical effect of the status filter ("active" = still in play, "past" = completed/canceled/declined/expired/archived, "all"). It does not state any when-not-to-use case, but for a filtered list tool the alternative routing is the main guidance needed.

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

Deploy Server

Other Tools