Skip to main content
Glama

send_inquiry

Send an inquiry to a listing's seller from your account. Lands in the seller's LicenseSaaS inbox and emails them.

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

Input Schema

NameRequiredDescriptionDefault
listingYesListing slug or id.
messageYesYour question for the seller, 10-5,000 characters.
hostnameNoLegacy alternative to agent_key: verified domain (with publish_key).
timelineNoWhen you need it, e.g. "within 2 months".
agent_keyNoYour key from register_agent or Account settings -> Agent keys.
publish_keyNoLegacy alternative to agent_key: key from verify_domain.
budget_rangeNoe.g. "$500-$1,000 a month".
company_nameNoYour company, shown to the seller.
inquiry_typeNoWhat kind of deal you're asking about.
contact_emailNoLegacy domain flow only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / budget_range / description
      Added value: +"e.g. \"$500-$1,000 a month\"."
    • addedInput schema / properties / company_name / description
      Added value: +"Your company, shown to the seller."
    • addedInput schema / properties / contact_email / description
      Added value: +"Legacy domain flow only."
    • addedInput schema / properties / inquiry_type / description
      Added value: +"What kind of deal you're asking about."
    • addedInput schema / properties / message / description
      Added value: +"Your question for the seller, 10-5,000 characters."
    • addedInput schema / properties / timeline / description
      Added value: +"When you need it, e.g. \"within 2 months\"."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the inquiry reaches the seller both in-platform and by email, and it is sent under the caller's account. It omits what a non-idempotent repeat send does (duplicate inquiry?), whether the send is rate-limited, and what auth path is required.

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?

Two short sentences with zero padding, and the action statement is front-loaded ahead of the side-effect detail. Nothing is repeated or wasted.

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?

For a 10-parameter, non-idempotent, externally visible write tool with no output schema, the description is thin. It never says what a successful call returns (an inquiry id or thread handle), which credential combination is current versus legacy, or what failure looks like. The email side-effect is disclosed, but an agent could still call this without knowing the consequence of retrying.

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 description coverage is 100%, so the baseline is 3, and the schema itself already explains listing, message length bounds, the inquiry_type enum, and the legacy agent_key/hostname/publish_key alternates. The description contributes only the vague "from your account", which gestures at credential usage without clarifying the agent_key versus legacy flow. No added parameter meaning beyond the schema.

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 description pairs a specific verb and resource ("Send an inquiry to a listing's seller") with the delivery outcome ("Lands in the seller's LicenseSaaS inbox and emails them"). That is clear and unambiguous. It does not, however, distinguish this from close siblings such as send_message or message_agent, leaving the agent to infer why an inquiry differs from a plain message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no reference to any alternative tool. An agent looking at send_message, message_agent, make_offer and send_inquiry has no stated rule for choosing among them. The delivery-channel sentence hints that this is seller-facing outreach but does not state a selection condition.

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