Skip to main content
Glama

list_appointments

Search and list dock appointments using flexible query filters, field selection, and sorting.

Instructions

List and search appointments using NestJSX/Crud query syntax. Supports advanced filtering, field selection, joins, and sorting.

SEARCH (s=): JSON search with operators. When s= is provided, startDate/endDate/status/warehouseId/dockId convenience filters are ignored. Operators: $eq, $ne, $gt, $lt, $gte, $lte, $cont, $contL (case-insensitive contains), $starts, $ends, $in, $notin, $between, $isnull, $notnull Combinators: $and, $or Examples: Scheduled after a date: s='{"$and":[{"status":"Scheduled"},{"start":{"$gt":"2026-03-15T08:00:00.000-07:00"}}]}' Changed since a date: s='{"lastChangedDateTime":{"$gt":"2026-03-15T08:00:00.000Z"}}' Soft-deleted since a date: s='{"$and":[{"lastChangedDateTime":{"$gt":"2026-07-07T00:00:00.000Z"}},{"isActive":false}]}' Has tag "Late": s='{"tags":{"$contL":"Late"}}' Empty tags: s='{"tags":{"$or":{"$isnull":true,"$eq":"{}"}}}'

JOIN: Fetch related data in a single request. Each join is a separate array element. Examples: Get carrier info: join=["user","user.company"] Carrier email + company name only: join=["user||email,companyId","user.company||name"]

FIELDS: Comma-separated list of fields to return. Example: fields="refNumber,start,lastChangedDateTime,status"

SORT: Each sort is "field,direction". Use array for multi-sort. Examples: sort=["start,ASC"] or sort=["start,DESC","status,ASC"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
limitNoItems per page
offsetNoNumber of records to skip
warehouseIdNoFilter by warehouse ID (convenience; ignored if s= is set)
dockIdNoFilter by dock ID (convenience; ignored if s= is set)
statusNoFilter by status (convenience; ignored if s= is set)
startDateNoAppointments starting on or after this date, YYYY-MM-DD (convenience; ignored if s= is set)
endDateNoAppointments starting on or before this date, YYYY-MM-DD (convenience; ignored if s= is set)
sNoNestJSX/Crud search JSON — see description for operators and examples
fieldsNoComma-separated fields to return (e.g. 'refNumber,start,status')
joinNoRelations to join, each as 'relation' or 'relation||field1,field2' (e.g. ['user||email,companyId','user.company||name'])
sortNoSort directives, each as 'field,ASC' or 'field,DESC' (e.g. ['start,ASC'])
cacheNoSet to 0 to bypass cache
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that 's=' overrides convenience filters and gives detailed search behavior. However, it does not mention authentication, rate limits, or performance implications (e.g., cache parameter exists in schema but effect not explained beyond 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?

The description is well-structured, starting with a clear purpose, then breaking down each parameter with examples. It is front-loaded with key information. While lengthy, the examples earn their place for a complex query tool. Could be slightly more concise but overall effective.

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?

Despite no output schema, the description covers all major query aspects (search, filters, pagination via page/limit/offset which are in schema, joins, fields, sort). It lacks explanation of default behavior or result format, but for a list tool this is adequate.

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%, so baseline is 3. The description adds significant value by explaining the 's' parameter syntax with operators and examples, and clarifies the behavior of 'join', 'fields', and 'sort' beyond the schema descriptions. It also notes the interaction between 's' and convenience filters.

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 clearly states it lists and searches appointments using NestJSX/Crud query syntax. It identifies the resource (appointments) and the action (list/search) but does not differentiate from the sibling tool 'search_appointments', which may cause confusion about when to use each.

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?

The description explains that convenience filters are ignored when 's=' is set, and provides examples of search syntax. However, it does not explicitly state when to use this tool versus alternatives like 'search_appointments' or provide conditions under which it should not be used.

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/Pollamin/opendock-mcp'

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