Skip to main content
Glama

Request a visit or appointment

request_visit

Requests a store visit or appointment on the day and time the customer chose. It reaches the business’s Appointments board as pending, and the team confirms it with the customer. Not for online-only stores. Only for businesses that take requests through AI assistants; others answer with their WhatsApp and chat links.

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": {
      "business": "<business>",
      "name": "<name>",
      "phone": "<phone>",
      "day": "<day>"
    },
    "name": "request_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesYYYY-MM-DD, today or later.
nameYes
noteNo
timeNo"morning", "afternoon", "evening", or a time like "17:30".
phoneYesThe customer’s phone or WhatsApp number with country code, e.g. +91 98765 43210, shared by the customer to be contacted.
businessYesThe business id from find_businesses, e.g. "carat-story".
product_idNo
product_titleNo

Output Schema

NameRequiredDescriptionDefault
idNo
statusYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real context beyond that: the request lands on the Appointments board as 'pending' and the team confirms with the customer, so the agent knows this is a non-final booking. It does not state what happens on duplicate submissions (relevant since idempotentHint=false) or what errors look like when a business does not accept AI requests.

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?

Three sentences, each doing a distinct job: what it does, what state it produces, and where it must not be used. The core action is front-loaded and no sentence is filler.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, resulting state, and eligibility. The remaining gap is the meaning of the optional product-linking parameters in an 8-parameter mutation tool, which the prose never touches.

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?

The required fields are documented in the schema (day, time, phone, business include patterns and examples), and the description only echoes 'day and time' without adding format meaning. With coverage at 50%, the description leaves name, note, product_id, and product_title — including how to attach a product to the visit — entirely unexplained in both schema and prose.

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 states a specific verb and resource ('requests a store visit or appointment') plus the timing scope ('the day and time the customer chose'). It is easy to separate from read-only siblings like get_business or find_businesses, but the nearest write sibling (create_lead) is never mentioned, so the boundary against it is left implicit.

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?

Clear negative conditions are given: 'Not for online-only stores' and 'Only for businesses that take requests through AI assistants', with a described fallback (answering with WhatsApp/chat links). What is missing is routing guidance to a sibling in the fallback case, e.g. whether to call ask_business or hand_off_to_team instead.

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