Skip to main content
Glama
Sign In
reservations-mcp

reservations-mcp

by kunalkhosla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tock_search

Search Tock venues by query. Returns guidance and a direct link to the venue (v1 stub; no live data).

Instructions

Search Tock venues. NOTE: Tock is a best-effort stub in v1 and returns guidance + a direct link rather than live data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "tock_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Without annotations, the description carries the full burden. It clearly discloses that the tool is a best-effort stub returning guidance and a link rather than live data, which is critical behavioral context beyond the basic search action.

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?

The description is one sentence plus a brief note, with no wasted words. The core purpose is front-loaded, and the note earns its place by conveying a key limitation.

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?

For a simple single-parameter stub tool, the description adequately covers purpose, output type, and limitation. However, it lacks any detail on acceptable input formats or what the direct link points to, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not elaborate on what the 'query' parameter should contain. While the param name is self-explanatory, the description adds no meaning beyond the schema field name.

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?

Description states 'Search Tock venues' with a specific verb and resource, and the 'Tock' scope clearly distinguishes it from Resy-focused sibling tools. The note about being a stub does not detract from purpose clarity.

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 Tock is the target and notes the stub limitation, but it does not explicitly state when to use this tool versus discover_restaurants or resy_search. No exclusions or alternative recommendations are provided, so guidance is only implied.

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