Skip to main content
Glama

Book a free site visit

request_site_visit

Book PaisaLocal's free site visit for an estimate from get_estimate. Call it first with estimate_id alone to get the open times, then again with one slot_date from that list plus the homeowner's name and email. Phone and the job's street address are optional; without an address PaisaLocal emails the homeowner for it. Only offered times can be booked. No deposit is taken.

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": {
      "estimate_id": "<estimate_id>"
    },
    "name": "request_site_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoHomeowner name (needed to book)
emailNoHomeowner email (needed to book)
phoneNoHomeowner phone (optional)
addressNoStreet address of the job with the house number (optional; PaisaLocal asks by email if left out)
slot_dateNoOne slot_date exactly as returned by a previous request_site_visit call
estimate_idYesestimate_id returned by get_estimate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent write. The description adds real context beyond them: no deposit is taken, unavailable slots cannot be booked, and omitting an address triggers PaisaLocal to email the homeowner. It stops short of saying what happens on a repeat call (the non-idempotent hint implies a second booking) or what the first call returns exactly.

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?

Four compact sentences, front-loaded with the purpose and the call sequence, then optionality, then constraints. Nothing is repeated from the schema or annotations verbatim, and no sentence is 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 six-parameter mutation with no output schema, the description covers the two-phase workflow, required vs optional inputs, and the no-deposit/no-guarantee constraints. It leaves error conditions (e.g. slot taken between calls) and the exact shape of the first response implicit, which keeps it just short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all six parameters are already documented, but the description adds operational meaning: name and email are required to complete a booking, phone and address are optional, and slot_date must be copied verbatim from a prior call's output. It also explains the fallback behavior when address is omitted, which the schema only hints at.

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?

States a specific verb and resource ("Book PaisaLocal's free site visit") plus the upstream dependency ("for an estimate from get_estimate"), which separates it cleanly from get_estimate and find_contractor.

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

Usage Guidelines5/5

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

Prescribes the exact two-call sequence: first with estimate_id alone to fetch open times, then with one slot_date from that list plus name and email. It also constrains the input ("Only offered times can be booked"), so there is no ambiguity about when and how to call it.

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