Skip to main content
Glama

SalonRenter for Muse

request_tour

Request a tour on an open slot when the owner has turned agent tours on. tourDate is YYYY-MM-DD and tourTime is HH:MM.

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": {
      "listingId": "<listingId>",
      "tourDate": "<tourDate>",
      "tourTime": "<tourTime>"
    },
    "name": "request_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
phoneNo
messageNo
tourDateYes
tourTimeYes
tourTypeNo
agentNameNo
listingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one useful prerequisite (owner must have agent tours on) but says nothing about side effects — whether the owner is notified, what happens on a taken slot, whether a request can be withdrawn, or rate limits — for what is clearly a mutation tool.

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?

Two tight, front-loaded sentences with no filler; the eligibility condition leads and the format notes follow. Brevity is bought at the cost of coverage, but nothing written is wasted.

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

Completeness2/5

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

A nine-parameter mutation tool with no annotations, no output schema, and 0% schema coverage needs far more than two sentences: contact-field semantics, tourType/agentName meaning, and the result of a failed or accepted request are all unaddressed.

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 9 parameters, and the description documents format only for tourDate and tourTime. The seven remaining inputs (listingId, name, email, phone, message, tourType, agentName) get no explanation of requiredness, format, or effect, though listingId is the key linkage the tool cannot work without.

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?

States a specific verb+resource ('Request a tour') plus a gating condition ('on an open slot when the owner has turned agent tours on'), which is enough to distinguish it from get_tour_availability, though the sibling is never named.

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?

The description gives a clear precondition for use (open slot, agent tours enabled on the listing), but offers no explicit routing to get_tour_availability for checking slots and no statement about when not to use it versus send_inquiry.

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