London Foster Realty LLC

Book a time

book_time

Books one open time for a buyer consultation or a listing appointment with London Foster Realty LLC. Needs the start of an open time, a first name, a phone or an email, and person_confirmed. Showings are not offered.

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": {
      "kind": "<kind>",
      "start": "<start>",
      "first_name": "<first_name>",
      "person_confirmed": "<person_confirmed>"
    },
    "name": "book_time"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	buyer_consult: the person wants to buy a home. listing_appt: the person wants to sell their home.
`note`	No	What they want, in their words (area, timing, the home).
`email`	No	Give a phone or an email.
`phone`	No	A US phone number. Give a phone or an email.
`start`	Yes	The start of an open time, exactly as listed.
`language`	No	The language the person wants.
`assistant`	No	Which assistant is sending this.
`last_name`	No
`first_name`	Yes
`person_confirmed`	Yes	true when the person agreed to this time and these details.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds useful context (a human must have confirmed the time and details, contact requires a phone or email) but says nothing about what happens if the slot is already taken or what the response looks like.

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 with no waste: purpose first, then required inputs, then the scope exclusion. Nothing is repeated or padded.

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 write tool with no output schema, the description covers purpose and prerequisites but leaves the agent without any expectation of the result or failure modes. It also omits mention of the optional fields, leaving half the surface for the schema to carry alone.

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 80%, so the schema largely documents itself; the description only restates the required inputs (start, first name, phone or email, person_confirmed) and the two appointment kinds. It adds no meaning for the remaining parameters (note, language, assistant, last_name).

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 gives a specific verb and resource ('Books one open time') plus the business scope (buyer consultation or listing appointment at London Foster Realty LLC) and an exclusion ('Showings are not offered'). It distinguishes itself from open_times (listing) and request_consultation only implicitly via the 'one open time' framing, without naming the siblings.

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?

'Needs the start of an open time' implies the agent must first obtain an open slot (e.g. via open_times) before calling, and 'Showings are not offered' is a clear when-not condition. It stops short of explicitly naming open_times or request_consultation as the alternative paths.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All London Foster Realty LLC tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?