Skip to main content
Glama

Place an order with Mini Split Reef

place_order

Send the customer's mini split order to Mini Split Reef. Someone reaches out to confirm the details and set the install time; no payment is taken here. Only call this when the user asks to order and gives their OWN name, phone, email and address or city.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "email": "<email>",
      "address_or_city": "<address_or_city>",
      "details": "<details>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer's full name
emailYesCustomer's email address
phoneYesCustomer's US phone number
detailsYesWhat they need: how many mini splits, which rooms, own unit or ours, anything else
preferred_timeNoPreferred day or time for the install or a call back
address_or_cityYesInstall address, or at least the city

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/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 downstream consequence: a human reaches out to confirm details and schedule install, and no payment is collected at this step. That is genuinely useful context an agent cannot derive from the annotation flags. It does not address duplicate submissions or what confirmation, if any, comes back to the caller.

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 clauses, front-loaded with the action, followed by the follow-up behavior and the precondition. Every sentence carries distinct information (what it does, who responds, no payment, entry criteria) with no redundancy.

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 six-parameter, five-required submission tool with full schema coverage and no output schema, the description covers purpose, consequence, payment policy, and preconditions. The only gap is what the caller gets back (a confirmation, a reference number, the required fields it returns), which would round out the picture.

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 every parameter is already documented in the input schema, and the description only echoes the required set ('their OWN name, phone, email and address or city'). The emphasis on the customer's own contact details adds a mild constraint on provenance, but no format or content guidance beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Send the customer's mini split order to Mini Split Reef') and names the destination system, making it immediately distinguishable from the read-only siblings (get_pricing, get_service_details, get_contact, ask_minisplit_reef). An agent can tell this is the transaction/lead-submission endpoint without opening the schema.

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 gating condition — 'Only call this when the user asks to order and gives their OWN name, phone, email and address or city' — which functions as both a when-to-use and an implicit when-not-to-use rule. It does not name an alternative tool for the fallback case or explain what to do when details are missing, so it stops short of the top band.

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