Skip to main content
Glama

Alina Szaputko — Online Consultation Booking

Send the client a consent confirmation link

request_client_consent

Sends a confirmation email to the client with the exact proposed online consultation details, booking rules and privacy notice. The client must open the link, review the details and personally confirm consent. This tool does not reserve a slot or initiate payment. Collect no clinical history.

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": {
      "name": "<name>",
      "email": "<email>",
      "date": "<date>",
      "time": "<time>",
      "consultationLanguage": "<consultationLanguage>"
    },
    "name": "request_client_consent"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nameYes
timeYes
emailYes
phoneNo
interfaceLanguageNo
consultationLanguageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds the meaningful context that this is an outbound client email requiring the client's personal action, and that it intentionally has no slot or payment side effect. It does not say whether repeat calls resend the email or how the confirmation comes back, which is the remaining gap for a non-idempotent outbound action.

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?

Four short sentences, purpose front-loaded in the first sentence, followed by the consent flow and the two explicit boundaries. No filler; the only slight dilution is the final safety line, which reads as a separate aside rather than integrated guidance.

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

Completeness3/5

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

There is no output schema, so the description could have said what the call returns (confirmation token, link, status), but it does not. Combined with zero parameter documentation on a 7-parameter tool, the definition is adequate on workflow behavior but incomplete on both inputs and return.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description carries the full burden and largely fails it. It alludes to consultation details, booking rules and privacy notice, but never maps meaning onto date, time, name, email, phone, interfaceLanguage versus consultationLanguage, or notes that interfaceLanguage is optional.

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: sends a confirmation email with the proposed consultation details, booking rules and privacy notice so the client can personally confirm consent. It also names the boundaries against when a booking actually happens (no slot reserved, no payment), which separates it from create_checkout_session without ambiguity.

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?

Explicit exclusions ('does not reserve a slot or initiate payment') tell the agent when this tool is the wrong choice and implicitly route to the checkout tool. It also constrains data collection ('Collect no clinical history'). What is missing is a positive statement of ordering, e.g. use this before create_checkout_session.

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