Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Check appointments

get_appointments_status
Read-onlyIdempotent

Whether a site takes appointments and, if not, the one next step — on/off, "pick a free time" or "ask for a time" mode, the weekly hours, the default appointment, where people can book (website, chat, voice — with why each is or is not working), how many are upcoming, waiting for confirmation, or waiting for the owner to pick a time. Pass include_setup_defaults: true before set_up_appointments: it adds the defaults a first setup would use for this business (appointment name and length, mode, weekly hours, time zone, channels). Changes nothing.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
include_setup_defaultsNotrue: also return the proposed setup defaults

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds useful return-scope detail (modes, weekly hours, default appointment, booking channel status, counts) and says `include_setup_defaults` only adds proposed defaults without changing anything.

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

Conciseness3/5

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

The information is relevant and mostly front-loaded, but the first sentence is a long run-on list of return fields that would be easier to scan if structured. The setup-defaults instruction is clear but appended as a second long clause.

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 burden of explaining returns, and it does so fairly comprehensively: appointment availability, mode, weekly hours, default appointment, booking-channel health, and upcoming/status counts. It could be stronger by explicitly contrasting with `list_appointments`, but it is sufficient for correct invocation.

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?

Schema description coverage is 100%, so baseline is 3. The description goes beyond the schema for `include_setup_defaults` by specifying what defaults are returned: appointment name and length, mode, weekly hours, time zone, and channels.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly conveys that this is a read/status tool for a site's appointment setup and activity, including modes, hours, booking channels, and counts. It names `set_up_appointments` as the follow-up action, though it does not differentiate from sibling tools like `list_appointments` or `manage_appointments`.

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 gives an explicit usage instruction: pass `include_setup_defaults: true` before `set_up_appointments` to preview first-setup defaults. It also states the call changes nothing, which helps confirm safe read usage. However, it does not say when to use this instead of `list_appointments` or `manage_appointments`.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources