Skip to main content
Glama

listing

by com.beycome
OverviewDiscussionsAdmin

beycome_showings

Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events).

Used once a listing is live. The API requires the date range, so it defaults to today → +90 days when omitted (from_date / to_date are YYYY-MM-DD, with to_date on or after from_date). prop_id filters to one listing; omit it for every listing the user owns.

The response always mixes ALL event kinds — each event carries a type field (showing / open_house / offer). There is no server-side type filter; when the user asks for one kind, filter on that field yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prop_idNoOptional — filter events to one property id; omit for all listings.
to_dateNoEnd of the calendar range (YYYY-MM-DD). Defaults to 90 days from today.
from_dateNoStart of the calendar range (YYYY-MM-DD). Defaults to today.
access_tokenYesBearer access token from beycome_signin_verify, or a previously saved token from your memory for this user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Bearer access token from beycome_signin_verify."New value: +"Bearer access token from beycome_signin_verify, or a previously saved token from your memory for this user."
  2. Changed4 schema fields changed
    • changedInput schema / properties / from_date / description
      Previous value: -"Start date for the calendar range (YYYY-MM-DD)."New value: +"Start of the calendar range (YYYY-MM-DD). Defaults to today."
    • changedInput schema / properties / prop_id / description
      Previous value: -"Filter events by property id."New value: +"Optional — filter events to one property id; omit for all listings."
    • changedInput schema / properties / to_date / description
      Previous value: -"End date for the calendar range (YYYY-MM-DD)."New value: +"End of the calendar range (YYYY-MM-DD). Defaults to 90 days from today."
    • removedInput schema / properties / type
      Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "showing",
-        "open_house",
-        "offer"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Filter by event type."
-}
  3. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Bearer access token from beycome_signin."New value: +"Bearer access token from beycome_signin_verify."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: response mixes all event kinds with a type field, no server-side type filter, and default date range applied. Could mention authentication details, but access_token is in schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single paragraph with clear, logical flow. No wasted words, but slight redundancy (e.g., 'Used once a listing is live' and later 'prop_id filters to one listing...'). Still effective and front-loaded.

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?

Given an output schema exists, the description adequately covers behavior (mixed types, defaults). No mention of error handling or rate limits, but these are often out of scope. Sufficient for a list-style tool with good schema coverage.

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%, baseline 3. Description adds meaning beyond schema: explains default values, format (YYYY-MM-DD), constraint (to_date on or after from_date), and prop_id filtering behavior. This enhances parameter understanding.

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 clearly states the tool retrieves a calendar of showings, open houses, and offer deadlines via GET /calendar/events, using a specific verb and resource. It distinguishes from siblings like beycome_offers by noting it returns all event types.

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?

Provides explicit usage context: 'Used once a listing is live.' Explains default date range behavior (today to +90 days) and when to omit prop_id for all listings. Advises client-side filtering when user asks for one event kind.

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

All listing toolsInspect
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