Skip to main content
Glama

Request an appointment

request_appointment

Ask an entry for an appointment for the user, such as a visit, a consultation or a demo. It is a request: the entry's owner confirms a time, or suggests another. Only for entries whose actions (get_entry_sections) list request_appointment. Ask the user for their name and email address. Nothing is sent by this call: the user sends it on Daawid's page, with a code Daawid emails them. Give the user the link from the answer.

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": {
      "entry": "<entry>",
      "requester": "<requester>",
      "purpose": "<purpose>",
      "preferredSlots": "<preferredSlots>"
    },
    "name": "request_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich entry: its ID or slug, from search or get_entry.
answersNoAnswers to the action's own questions (get_entry_sections), by their keys.
purposeYesWhat it is for, in the user's words and language. Don't add what they didn't say, such as features from the entry.
actionIdNoWhich of its actions of this kind (get_entry_sections), when it has several.
requesterYes
offeringIdNoWhich of the entry's offerings (get_entry_sections) it is about, if one.
postalCodeNoThe postal code, when it is at the user's place or the action asks for one.
idempotencyKeyNoYour own key for this request: the same key and details within 24 hours give the same request.
preferredSlotsYesTimes that suit the user: 1 to 5 windows.

Output Schema

NameRequiredDescriptionDefault
urlNo
kindYes
entryYes
runIdNo
statusYes
summaryYes
expiresAtNo
confirmUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false), the description discloses the two-phase flow: this call only records a request, the entry's owner confirms or counter-proposes a time, and the actual send happens on Daawid's page with an emailed code. Telling the agent 'Nothing is sent by this call' and to hand back the link from the answer prevents the most likely misinterpretation of an open-world, non-read-only 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?

Five short sentences, front-loaded with the purpose and followed by the constraint, the confirmation semantics, the user-input requirement and the two-step caveat — no filler. The phrasing is slightly telegraphic, but every sentence carries distinct information.

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 9-parameter, nested-object, open-world mutation with an output schema, the description covers the prerequisite lookup, the required user inputs and what the response is used for (the link). It leaves the idempotency-key retry behavior undiscussed, though the schema documents it, so it is nearly but not fully complete.

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 89%, so entry, purpose, requester, preferredSlots and answers are already documented in structured fields with examples. The description only echoes the schema's 'ask them; don't guess' instruction for name and email and adds no semantics for actionId, offeringId, postalCode or idempotencyKey, so baseline 3 applies.

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 first sentence gives a specific verb and resource ('Ask an entry for an appointment') and scopes it with examples (visit, consultation, demo), which separates it from a callback or a quote by domain. It stops short of naming the sibling request tools to say how the appointment request differs from them, so it is clear but not fully differentiated.

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 precondition — 'Only for entries whose actions (get_entry_sections) list request_appointment' — and names the call that supplies that check, which is real routing guidance. It also tells the agent to ask the user for name and email, but gives no guidance on choosing between this and request_callback/request_quote when several are offered.

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