Skip to main content
Glama

Ask the mover to visit (or call) instead of filming.

request_visit

Ask the mover to visit (or call) instead of filming. Free, never billed, creates no job; the mover gets it by email, on the dashboard and as visit.requested. Scope: quote.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe customer's name
noteNoOptional, up to 300 characters
emailNoOptional. If given, the customer gets one confirmation email
phoneYesA number the mover can call: 7 to 15 digits, any formatting
originNoOne end of the move, as the customer gives it.
windowsNoGood times for the mover to come or call
dwellingNoA `dwelling` from GET /home-profiles
move_dateNoYYYY-MM-DD
destinationNoOne end of the move, as the customer gives it.
ballpark_low_centsNoThe range the customer was shown, if any (context only)
ballpark_high_centsNoThe range the customer was shown, if any (context only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Adds real value beyond the annotations: it is free and never billed, creates no job, and the mover is notified by email, on the dashboard, and via the `visit.requested` event. This clarifies that a request record is written without committing to a job, consistent with readOnlyHint=false and destructiveHint=false. It does not say what the caller receives back (no output schema), which keeps it from a higher score.

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 tightly packed sentences with the purpose and its contrast to filming front-loaded, followed by cost/notification behavior and scope. No 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?

For a 11-parameter tool with nested address objects and no output schema, the description covers cost, side effects, notification channels and funnel scope well, while the schema handles parameters. The remaining gap is the absence of any statement about what the call returns (e.g., a request id or status).

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 one of the 11 parameters (including the nested origin/destination objects) is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Names a concrete action and outcome: ask the mover to visit or call rather than film, and scopes it to "quote". This clearly separates it from the filming/hand-off path, though it does not explicitly distinguish it from funnel siblings like request_booking or submit_job.

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?

Gives a positive usage cue ('instead of filming') and a stage constraint ('Scope: quote'), so an agent knows the situation that calls for it. It stops short of naming when not to use it or which sibling covers the booking path.

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