Skip to main content
Glama
ashev87

Propstack MCP

list_events

List calendar events from Propstack, including property viewings and client meetings. Filter by date range, state (scheduled, completed, cancelled), broker, client, or property to find specific appointments.

Instructions

List calendar events (Termine) in Propstack.

Events are appointments like property viewings, client meetings, notary appointments, etc.

Use this tool to:

  • See what's scheduled this week (starts_at_after/starts_at_before)

  • List upcoming viewings for a broker (broker=ID)

  • Find cancelled appointments (state="cancelled")

  • Check recurring events

  • Filter by contact (client=ID) or property (property=ID)

  • Answer "what viewings are scheduled this week?"

Event states:

  • neutral: Scheduled, not yet happened

  • took_place: Completed

  • cancelled: Was cancelled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag/group ID (Merkmal)
pageNoPage number (default: 1)
stateNoEvent state: neutral (scheduled), took_place, cancelled
brokerNoFilter by broker ID
clientNoFilter by contact ID
projectNoFilter by project ID
per_pageNoResults per page (default: 25)
propertyNoFilter by property ID
note_typeNoFilter by event category/type ID
recurringNoFilter for recurring events only
ends_at_afterNoEvents ending after this date/time (ISO 8601)
ends_at_beforeNoEvents ending before this date/time (ISO 8601)
starts_at_afterNoEvents starting after this date/time (ISO 8601, e.g. '2025-01-01')
starts_at_beforeNoEvents starting before this date/time (ISO 8601, e.g. '2025-12-31')
Behavior3/5

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

With no annotations, the description carries full burden. It covers event states but omits pagination behavior, result ordering, scope of results (user-specific?), and whether it is read-only. Some key behavioral aspects are missing.

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?

The description is structured with a definition, bulleted use cases, and event states. It is informative but could be slightly more concise without losing clarity.

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?

Given 14 parameters, no output schema, and no annotations, the description covers usage and states but fails to describe the return format, default pagination, or sorting behavior, leaving gaps for an AI agent.

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%, yet the description adds meaningful context by illustrating how parameters are used in practice (e.g., 'List upcoming viewings for a broker') and explaining event states, exceeding the schema's bare descriptions.

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 it lists calendar events in Propstack, provides examples of event types, and enumerates specific use cases. It differentiates from sibling tools like search_activities by focusing on events.

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 includes explicit use cases and lists event states, but does not mention when to avoid using this tool or suggest alternatives for non-event listings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ashev87/propstack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server