Skip to main content
Glama
Sign In

listing

by com.beycome
OverviewDiscussionsAdmin

View showings calendar

beycome_showings
Read-only

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

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

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.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses non-obvious behavior: the date range defaults to today → +90 days when omitted, and the response always mixes all event kinds with no server-side type filter, forcing the agent to filter client-side. That last point is exactly the kind of trait annotations cannot convey.

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?

Front-loads the purpose, then usage stage, then parameter behavior, then the response caveat. Every sentence adds information an agent needs; nothing is redundant padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, yet the description still supplies the critical structural fact (the type field and its values) plus default/filter behavior. Nothing needed to invoke this correctly is missing.

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 already 100% (formats and defaults are documented there), so the baseline is 3. The description goes further by adding the ordering constraint that to_date must be on or after from_date, which is not in the schema.

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+resource combination — a calendar of showings, open houses, and offer deadlines — and even names the lifecycle stage ('post-publish'). An agent can distinguish this from sibling beycome_offers because the calendar explicitly mixes event kinds rather than being an offers list.

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?

'Used once a listing is live' gives clear context for when this tool applies. It does not, however, name an alternative tool or an explicit when-not condition, so it falls short of the routing guidance a 5 requires.

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