Skip to main content
Glama

Run an isolated scheduling demo

run_public_demo

Run a complete, anonymous demo with a fictional team in a single call. No account, OAuth, login, session ID, token, workspace ID or setup call is required. The result includes a proposed roster, coverage and hard-constraint checks, soft-preference exceptions and a manager next step. Each call is isolated; its schedule is not saved or published. If an instruction is ambiguous, return the blocker rather than silently ignoring it. Use fictional information 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": "run_public_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
demandsNoOptional explicit fictional shift requirements. Each row can include day, role, start, end, shift, and required or min_required/max_required headcount. Omit to use sample shifts.
industryNoBusiness type used to select the fictional sample team and shift templates.restaurant
team_sizeNoNumber of synthetic workers, from 4 to 12; defaults to the selected industry's sample size.
period_modeNoSchedule length: week or month. Defaults to one week.week
period_startNoOptional date in YYYY-MM-DD format inside the requested week or month; otherwise the next full period is selected.
manager_requestNoOptional natural-language scheduling instructions for this fictional team only. Ambiguous requests stop for review; never include real staff or business data.
coverage_per_shiftNoWorkers required on each enabled shift for each operating day.
time_limit_secondsNoSolver time budget, from 0.1 to 10 seconds. Defaults to 2 seconds.
operating_days_per_weekNoNumber of open days, starting Monday. For example, 5 means Monday through Friday.

Output Schema

NameRequiredDescriptionDefault
demoYes
storeYes
periodYes
privacyNo
scenarioYes
workflowYes
quality_checkYes
parsed_requestNo
schedule_previewYes
proposed_settingsNo
feedback_next_stepNo
optional_discoveryNo
optional_next_stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / schedule_preview / properties / employee_hours
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / workflow / properties / ready_for_manager_review
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed12 schema fields changed
    • changedInput schema / properties / coverage_per_shift / description
      Previous value: -"Workers required for each enabled shift."New value: +"Workers required on each enabled shift for each operating day."
    • changedInput schema / properties / demands / description
      Previous value: -"Optional explicit fictional shift requirements; otherwise generated from the chosen industry and coverage."New value: +"Optional explicit fictional shift requirements. Each row can include day, role, start, end, shift, and required or min_required/max_required headcount. Omit to use sample shifts."
    • addedInput schema / properties / demands / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / demands / items / properties
      Added value: +{
      +  "day": {
      +    "description": "Shift date in YYYY-MM-DD format.",
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "end": {
      +    "description": "Local shift end time in 24-hour HH:MM format.",
      +    "pattern": "^\\d{2}:\\d{2}$",
      +    "type": "string"
      +  },
      +  "max_required": {
      +    "description": "Maximum headcount to assign to this shift.",
      +    "maximum": 100,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "min_required": {
      +    "description": "Minimum headcount needed for this shift.",
      +    "maximum": 100,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "required": {
      +    "description": "Exact headcount when min_required and max_required are omitted.",
      +    "maximum": 100,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "role": {
      +    "description": "Role required for this shift; defaults to Associate.",
      +    "type": "string"
      +  },
      +  "shift": {
      +    "description": "Optional short shift label.",
      +    "type": "string"
      +  },
      +  "start": {
      +    "description": "Local shift start time in 24-hour HH:MM format.",
      +    "pattern": "^\\d{2}:\\d{2}$",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / industry / description
      Added value: +"Business type used to select the fictional sample team and shift templates."
    • changedInput schema / properties / manager_request / description
      Previous value: -"Optional natural-language scheduling instruction for this fictional team only."New value: +"Optional natural-language scheduling instructions for this fictional team only. Ambiguous requests stop for review; never include real staff or business data."
    • changedInput schema / properties / operating_days_per_week / description
      Previous value: -"First N days of the week, starting Monday."New value: +"Number of open days, starting Monday. For example, 5 means Monday through Friday."
    • addedInput schema / properties / period_mode / description
      Added value: +"Schedule length: week or month. Defaults to one week."
    • changedInput schema / properties / period_start / description
      Previous value: -"Optional ISO start date; otherwise choose the next full week or month."New value: +"Optional date in YYYY-MM-DD format inside the requested week or month; otherwise the next full period is selected."
    • changedInput schema / properties / team_size / description
      Previous value: -"Synthetic workers; defaults to the selected industry's sample size."New value: +"Number of synthetic workers, from 4 to 12; defaults to the selected industry's sample size."
    • addedInput schema / properties / time_limit_seconds / description
      Added value: +"Solver time budget, from 0.1 to 10 seconds. Defaults to 2 seconds."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "demo": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "industry": {
      +          "enum": [
      +            "auto-repair",
      +            "clinic",
      +            "restaurant",
      +            "retail",
      +            "warehouse"
      +          ],
      +          "type": "string"
      +        },
      +        "isolated_for_this_call": {
      +          "const": true,
      +          "type": "boolean"
      +        },
      +        "published": {
      +          "const": false,
      +          "type": "boolean"
      +        },
      +        "sample_data_only": {
      +          "const": true,
      +          "type": "boolean"
      +        },
      +        "saved": {
      +          "const": false,
      +          "type": "boolean"
      +        },
      +        "status": {
      +          "enum": [
      +            "completed",
      +            "needs_attention"
      +          ],
      +          "type": "string"
      +        },
      +        "workspace_handle_exposed": {
      +          "const": false,
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "status",
      +        "industry",
      +        "sample_data_only",
      +        "isolated_for_this_call",
      +        "workspace_handle_exposed",
      +        "saved",
      +        "published"
      +      ],
      +      "type": "object"
      +    },
      +    "feedback_next_step": {
      +      "type": "string"
      +    },
      +    "optional_discovery": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "optional_next_steps": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "parsed_request": {
      +      "additionalProperties": true,
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "period": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "days": {
      +          "minimum": 1,
      +          "type": "integer"
      +        },
      +        "end": {
      +          "format": "date",
      +          "type": "string"
      +        },
      +        "mode": {
      +          "type": "string"
      +        },
      +        "start": {
      +          "format": "date",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "mode",
      +        "start",
      +        "days"
      +      ],
      +      "type": "object"
      +    },
      +    "privacy": {
      +      "type": "string"
      +    },
      +    "proposed_settings": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "quality_check": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "all_required_shifts_covered": {
      +          "type": "boolean"
      +        },
      +        "duplicate_assignments": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "hard_constraint_violations": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "hard_constraints_passed": {
      +          "type": "boolean"
      +        },
      +        "no_duplicate_assignments": {
      +          "type": "boolean"
      +        },
      +        "soft_preference_violation_count": {
      +          "type": "integer"
      +        },
      +        "solver_status": {
      +          "type": "string"
      +        },
      +        "uncovered_shift_slots": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "scenario": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "coverage_per_shift": {
      +          "type": "integer"
      +        },
      +        "operating_days_per_week": {
      +          "type": "integer"
      +        },
      +        "team_size": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "schedule_preview": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "assignments": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "diagnostics": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "total_cost": {
      +          "type": "number"
      +        },
      +        "total_minutes": {
      +          "type": "integer"
      +        },
      +        "unfilled": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "store": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "id": {
      +          "type": "integer"
      +        },
      +        "is_sample_data": {
      +          "type": "boolean"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "workflow": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "completed": {
      +          "type": "boolean"
      +        },
      +        "completed_steps": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "manager_confirmation_required": {
      +          "type": "boolean"
      +        },
      +        "next_action": {
      +          "type": "string"
      +        },
      +        "published": {
      +          "const": false,
      +          "type": "boolean"
      +        },
      +        "saved": {
      +          "const": false,
      +          "type": "boolean"
      +        },
      +        "status": {
      +          "type": "string"
      +        },
      +        "steps": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "status",
      +        "completed",
      +        "saved",
      +        "published"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "demo",
      +    "workflow",
      +    "store",
      +    "period",
      +    "scenario",
      +    "schedule_preview",
      +    "quality_check"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / period_start / description
      Previous value: -"Optional ISO date; omitted dates use the demo's current scheduling period."New value: +"Optional ISO start date; otherwise choose the next full week or month."
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses the behavior that matters most: each call is isolated and the resulting schedule is neither saved nor published, so repeated calls are independent. It also lists what the response contains (proposed roster, coverage and hard-constraint checks, soft-preference exceptions, manager next step) and confirms no auth or setup is needed, which the annotations alone do not convey.

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?

Sentences are short and front-loaded, leading with what the tool does and its isolation guarantee. There is minor redundancy between "anonymous demo with a fictional team" and the closing "Use fictional information only," which repeats the same constraint in weaker form.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with a full output schema, everything an agent needs before calling is present: no prerequisites, isolation semantics, synthetic-data requirement, and ambiguity behavior. Return-value detail is supplied by the output schema and the description only summarizes it, which is appropriate.

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 defaults, ranges, and enum values are already documented in the schema. The description adds only indirect meaning by tying ambiguity handling to the free-text manager_request and reinforcing the fictional-data restriction; it names no specific parameter, so the baseline of 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?

A concrete verb and resource are front-loaded: "Run a complete, anonymous demo with a fictional team in a single call." The scope (synthetic team, isolated, single call) is specific enough that an agent can distinguish it from the sibling tools, which deal with product info, feedback, and share drafts rather than scheduling.

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?

It states the preconditions clearly (no account, OAuth, login, session ID, token, workspace ID, or setup call) and gives a hard constraint: "Use fictional information only." It also tells the agent what to do on ambiguity ("return the blocker rather than silently ignoring it"). What is missing is any explicit statement of when NOT to use it or which sibling to pick instead, so it stays at 4 rather than 5.

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