Skip to main content
Glama
WYRE-AI

timezest-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

timezest_scheduling_list

List scheduling requests from TimeZest with optional status and TQL filters to review appointment requests and manage scheduling workflows.

Instructions

List scheduling requests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoTQL filter string (e.g., "createdAt:>=2024-01-01")
statusNoFilter by TimeZest status: new, sent, scheduled, cancelled, closed. Legacy aliases are accepted and mapped: pending→sent, booked→scheduled, completed→closed. Sent as a TQL filter (scheduling_request.status EQ <value>). TimeZest ignores a status query parameter.
pageSizeNoHow many records to return from this page (1–20). TimeZest list pages are fixed at 20 and ignore a page_size query parameter; smaller values truncate that page. Larger values still return at most one TimeZest page (20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.1
    • changedInput schema / properties / pageSize / description
      Previous value: -"Number of results per page (default: 50, max: 100)"New value: +"How many records to return from this page (1–20). TimeZest list pages are fixed at 20 and ignore a page_size query parameter; smaller values truncate that page. Larger values still return at most one TimeZest page (20)."
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status"New value: +"Filter by TimeZest status: new, sent, scheduled, cancelled, closed. Legacy aliases are accepted and mapped: pending→sent, booked→scheduled, completed→closed. Sent as a TQL filter (scheduling_request.status EQ <value>). TimeZest ignores a status query parameter."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "pending",
-  "booked",
-  "cancelled",
-  "completed"
-]New value: +[
+  "new",
+  "sent",
+  "scheduled",
+  "cancelled",
+  "closed",
+  "pending",
+  "booked",
+  "completed"
+]
  2. Addedv3.0.0

TDQS

C2.8/5.0
Behavior2/5

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

There are no annotations, so the description must disclose behavioral traits itself. 'List scheduling requests' only implies a non-mutating read operation and says nothing about important behaviors such as pagination being fixed at 20 records, the `status` query parameter being ignored by TimeZest, or the legacy status alias mapping. These details are buried in parameter descriptions rather than surfaced in the tool description.

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

Conciseness3/5

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

The description is extremely concise and front-loaded, with no wasted words. However, it is under-specified: it omits any mention of filtering, status handling, pagination, or return value, so its brevity comes at the cost of usefulness. It is a clear lead-in but not a sufficient definition on its own.

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

Completeness2/5

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

With no annotations and no output schema, the description alone is not enough for an agent to confidently understand the tool's behavior and selection context. The parameter schema covers invocation details well, but the definition still lacks an explicit statement about what a scheduling request is, what the list response contains, or how this list call relates to the other scheduling tools.

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%, so the baseline is 3. The tool description adds nothing about parameters, but the input schema already provides rich detail for `filter`, `status`, and `pageSize`, including TQL syntax, status aliases, and pagination constraints. No additional parameter meaning is needed from the description.

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 uses a specific verb ('List') with a clear resource ('scheduling requests'), so an agent can tell this is a read operation for multiple items. It is distinguished from the singular `timezest_scheduling_get` and from `timezest_scheduling_create_request` / `timezest_scheduling_cancel` by its list-oriented wording, though it does not explicitly state those contrasts.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives such as `timezest_scheduling_get` or `timezest_scheduling_create_request`. There is no statement about using it for browsing/filtering requests or about when another scheduling tool would be more appropriate, so the agent must infer usage from the name and sibling list.

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

Deploy Server

Other Tools