Skip to main content
Glama

update_appointment_review_settings

Idempotent

Set whether completed appointments queue customer review requests and set the HTTPS review URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "enabled": "<enabled>",
      "reviewUrl": "<reviewUrl>"
    },
    "name": "update_appointment_review_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
reviewUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this is a non-destructive, idempotent, closed-world write with readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context by tying the setting to completed appointments and requiring the URL to be HTTPS, but it omits whether disabling suppresses already-queued requests, what permissions are needed, and what is returned after the update.

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

Conciseness5/5

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

A single tight sentence with the two settings front-loaded and no padding. Every clause maps to a parameter or a behavior.

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?

For a two-parameter settings tool with annotations covering the mutation profile and no output schema, this is largely sufficient. The only meaningful gap is the absence of guidance on reading current values versus updating them, which the sibling get_appointment_review_settings would cover.

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 0%, so the description carries the burden, and it does explain both parameters in plain terms: enabled gates queuing of review requests for completed appointments, and reviewUrl must be HTTPS. That HTTPS constraint is genuinely new information beyond the schema, which only declares a 2048-character string, but URL format, validation behavior, and the meaning of invalid or rejected values are not addressed.

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 gives a specific verb ("Set") plus the two concrete resources it controls (whether completed appointments queue review requests, and the HTTPS review URL). This implicitly separates it from the read counterpart get_appointment_review_settings, but it never names that sibling or any other alternative explicitly.

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 implied rather than stated: an agent can infer this is the write-side counterpart for configuring review requests, but there is no explicit "use this when..." guidance, no prerequisites, and no mention of the get_* alternative for reading current values.

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