Skip to main content
Glama
Sign In
@striderlabs/mcp-opentable

@striderlabs/mcp-opentable

by noahelson208-prog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

opentable_logout

Log out of OpenTable by clearing stored session cookies. Resets authentication state to enable a fresh login or switch accounts.

Instructions

Clear the stored OpenTable session cookies. Use this to log out or reset the authentication state.

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": "opentable_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description must fully disclose behavior. It does state the core effect (clearing cookies, resetting auth state) but omits potential side effects like whether it invalidates server-side sessions, makes network calls, or is idempotent. This is adequate but not comprehensive.

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 two sentences with no redundant words. It front-loads the action ('Clear the stored OpenTable session cookies') and adds a brief usage note, all in under 30 words.

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 zero-parameter logout tool with no output schema, the description covers the essential purpose and usage. It could elaborate on edge cases (e.g., behavior when already logged out) but is sufficiently complete for typical use.

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?

The tool has zero parameters, so schema coverage is trivially 100%. Per the rubric, a baseline of 4 is appropriate; the description adds no parameter-specific details but none are needed.

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 the tool's function: 'Clear the stored OpenTable session cookies' and explicitly equates it to 'log out or reset the authentication state.' This is a specific verb-resource pairing that distinguishes it from siblings like opentable_login and opentable_status.

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 statement 'Use this to log out or reset the authentication state' provides clear guidance on when to use the tool. Though it doesn't mention specific alternatives, the purpose is unambiguous and aligns with the sibling context (e.g., login handles the opposite action).

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