London Foster Realty LLC

Request a consultation

request_consultation

Sends London Foster Realty LLC a request for a buyer consultation or a listing appointment. An agent reaches out to set a time; nothing is booked.

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

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.
`name`	Yes
`about`	No	What they want, in their words.
`email`	No
`phone`	No	Give a phone or an email.
`times`	No	Days and times they prefer, in their words.
`language`	No	The language the person wants.
`assistant`	No	Which assistant is sending this.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already indicate this is a non-read-only, non-destructive operation, and the description adds the important behavioral detail that it only sends a request and does not book an appointment. It also discloses the human follow-up step, though it does not describe confirmation behavior or any submission limits.

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?

The description is two tight sentences with the core action and the no-booking constraint front-loaded. Every sentence adds useful information without repetition or 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 an 8-parameter request form with no output schema, the description gives the key outcome: a request is sent and an agent follows up without booking anything. It does not explain required contact methods or what confirmation the caller receives, but the schema covers most parameter-level detail needed to invoke it.

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?

With 75% schema description coverage, most parameters are already explained in the schema, and the description reinforces the distinction between buyer consultation and listing appointment. It adds little meaning beyond the schema for contact details, timing preferences, or optional fields, so the baseline score is appropriate.

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 states a specific action and resource: sending London Foster Realty LLC a buyer consultation or listing appointment request. It also immediately distinguishes this from booking by saying an agent reaches out and nothing is booked, which clearly separates it from the sibling book_time tool.

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?

The description makes the usage context clear: use this to request a consultation or listing appointment rather than to reserve a specific time. However, it does not explicitly name book_time as the alternative for actual scheduling, so the routing guidance is strong but not fully explicit.

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?