Skip to main content
Glama
Sign In
tock-mcp

tock-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tock_list_reservations

Read-only

List the signed-in user's Tock reservations—upcoming, past, or canceled—with venue, date/time, party size, and experience; choose a brief view for one line per reservation.

Instructions

List the signed-in user's Tock reservations (upcoming, past, or canceled) with venue, date/time, party size, and experience. Pass view: "brief" for one line per reservation. Requires a browser tab signed in to exploretock.com via the ContextMint Bridge extension.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tock_list_reservations"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns the reservation records as JSON; "brief" returns one line per reservation: venue: experience (party of N) — <ISO date-time or "no date"> — <upcoming|past|cancelled>, inside the untrusted-data envelope as data: string[], with a "-- none" note for an empty page and "-- more" for a full one.
limitNoMax to return (default 30).
offsetNoPagination offset (default 0).
statusNoWhich reservations to list (default upcoming).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "\"full\" (default) returns the reservation records as JSON; \"brief\" returns one line per reservation: venue: experience (party of N) — <ISO date-time or \"no date\"> — <upcoming|past|cancelled>, inside the untrusted-data envelope as data: string[], with a \"-- none\" note for an empty page and \"-- more\" for a full one.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that a browser tab signed in to exploretock.com via the ContextMint Bridge extension is required, which is not derivable from annotations. It does not discuss pagination behavior or rate limits beyond what the schema states.

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?

Two tight sentences, front-loaded with the core purpose and followed by the useful brief-view note and the authentication prerequisite. Every sentence carries information, though the auth requirement could arguably be placed after the view detail for slightly better flow.

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?

The tool is a read-only list operation with no output schema, so the description should describe return shape; it names the fields returned and the brief format, which is helpful. However, it does not explain pagination semantics (limit/offset interplay), the default status filter behavior, or what the full JSON record structure looks like, leaving some gaps for an agent invoking it.

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% and all four parameters are documented with defaults and enums, so the schema carries the semantic load. The description adds a small amount by highlighting the brief view output shape (one line per reservation), but it does not explain status filtering, limit/offset interaction, or the default upcoming filter beyond restating the enum.

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 and resource ("List the signed-in user's Tock reservations"), enumerates scope (upcoming, past, or canceled) and returned fields (venue, date/time, party size, experience). It is clearly distinguishable from siblings like tock_get_availability or tock_verify_reservation, which target availability and single reservations.

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 implies when to use it (listing one's own reservations) and names the view: "brief" option for a compact form, but it gives no explicit when-to-use vs. when-not guidance and doesn't point to an alternative sibling for cases this tool doesn't cover. The authentication prerequisite is mentioned, which helps, but the routing guidance is only implicit.

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