Skip to main content
Glama

London Foster Realty LLC

Open times

open_times
Read-only

Lists the open times for a buyer consultation or a listing appointment with London Foster Realty LLC. 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>"
    },
    "name": "open_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many open days to list (1 to 14, default 7).
fromNoFirst day to look at, MM/DD/YYYY. Leave out for the next open days.
kindYesbuyer_consult: the person wants to buy a home. listing_appt: the person wants to sell their home.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine domain exclusion (showings are not offered) that the annotations do not convey, but says nothing about slot staleness, timezone, or what the listing actually returns.

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 sentences, zero filler, with the resource and scope front-loaded and the negative constraint placed where it will be read. Nothing is repeated from the title or schema.

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 three-parameter read-only tool with no output schema, this is close to sufficient, but it leaves open how the result relates to the booking siblings and gives no hint about availability semantics. An agent still has to guess the workflow placement.

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%, including an enum explanation for kind and range/default notes for days and from, so the schema carries the parameter burden. The description adds no additional parameter meaning beyond what is already structured, which is the baseline case.

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 pairs a specific verb ("Lists") with a specific resource ("open times") and scopes it to two named appointment kinds, so the agent knows exactly what comes back. It falls short of a 5 because it does not explicitly contrast itself with the available siblings (book_time, request_consultation).

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the availability-lookup step that precedes book_time, and "Showings are not offered" rules out one case. There is no explicit statement of when to call this versus request_consultation or check_area.

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