Skip to main content
Glama

SalonRenter for Muse

send_inquiry

Send the listing owner an inquiry as the signed-in renter. Search does not need an account. This does.

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>"
    },
    "name": "send_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailNo
phoneNo
messageNo
agentNameNo
listingIdYes
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the authentication requirement and that the sender identity is implicit, but says nothing about delivery behavior, validation failures, whether fields like email/phone are captured or required, retry semantics, or rate limits for a write-style send.

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 short sentences, front-loaded with the action and followed by the key constraint. No filler; the terse contrast sentence is doing genuine work.

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 7-parameter write-style tool with no annotations, no output schema, and zero parameter documentation leaves too much unspecified for an agent to call it confidently, particularly around optional contact fields and the idempotency key.

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 must compensate and it largely does not. The phrase 'as the signed-in renter' hints that sender identity comes from the session rather than name/email/phone, but nothing explains message, agentName, idempotencyKey, or why only listingId is required.

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 and resource: send an inquiry to the listing owner, acting as the signed-in renter. That is concrete enough to distinguish it from read tools like get_listing, though it does not explicitly contrast with the tour-request sibling.

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 line 'Search does not need an account. This does.' gives the agent a real decision rule: this tool requires authentication and the others may not. However, it offers no guidance on when to prefer this over request_tour or what to do when the user is unauthenticated.

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