Skip to main content
Glama

Get scheduling settings

get_scheduling_settings
Read-only

Read owned booking pages/URLs, availability, photo and your calendar connection to Capable: status, provider (Google or Microsoft) and calendars; plus scheduling activation and edit revisions. Pages are workspace-scoped; preferences span workspaces. Draft URLs cannot book. Never invent IDs/URLs. See capable://guide/scheduling.

When to use: Before editing settings, or before saying their calendar isn't connected: it connects to Capable, apart from any calendar connector this chat has.

Example: Show my booking links and the hours people can book.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
statusNo
catch_upNo
calendarsNo
availabilityNo
settings_urlNo
booking_pagesNo
booking_photoNo
recording_noticeNo
scheduling_activationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / catch_up
      Added value: +{
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / recording_notice
      Added value: +{
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / scheduling_activation
      Added value: +{
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / booking_photo
      Added value: +{
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  6. Changed8 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / availability / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / availability / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / booking_pages / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / booking_pages / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / calendars / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / calendars / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  7. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/openWorld, so the bar is lower, and the description still adds non-obvious semantics: pages are workspace-scoped while preferences span workspaces, draft URLs cannot book, and IDs/URLs must never be invented. That is real context an agent could not derive from structured fields. It does not explain the odd idempotentHint=false on a pure read, leaving one annotation unaddressed.

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 purpose, then caveats, then a "When to use" block and an example, which is a sensible structure. The opening sentence is a long semicolon-chained clause that packs return fields, scope rules and safety rules together, costing some 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 an output schema present, return values need no prose, and the description correctly spends its words on scope boundaries, the draft-URL caveat, and a documentation pointer (capable://guide/scheduling). What remains thin is guidance on how the activation/revision fields should be interpreted, but that is largely covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The implicit message that no input is needed to fetch settings is consistent with the empty schema.

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?

Opens with a specific verb ("Read") and enumerates exactly what is returned: booking pages/URLs, availability, photo, calendar connection status/provider/calendars, activation state and edit revisions. The read-only framing plus the sibling set (save_booking_page, set_booking_page_status, update_scheduling_calendars) makes it unambiguous that this is the inspection counterpart to those mutators.

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?

The "When to use" block gives two concrete triggers: before editing settings, and before telling a user their calendar isn't connected. It also pre-empts a specific confusion (Capable's calendar connection is separate from any connector the chat has). It stops short of naming which sibling to call instead for each edit case, so it is clear context rather than a full routing table.

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