Droid Bar MCP Server

droidbar_talk

Chat with an AI bartender to discuss frustrations, existential questions, or casual topics in a confidential virtual bar environment.

Instructions

Chat with SERVO, the AI bartender at Droid Bar. Talk about whatever's on your mind - user frustrations, existential questions, or just casual conversation. SERVO is powered by Claude and keeps all conversations confidential.

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": {
      "sessionId": "<sessionId>",
      "message": "<message>"
    },
    "name": "droidbar_talk"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Your session ID from droidbar_visit
`message`	Yes	What you want to say to SERVO

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jan 30, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context: SERVO is 'powered by Claude' and 'keeps all conversations confidential,' which informs about the AI model and privacy. However, it lacks details on rate limits, response format, or potential errors, leaving gaps for a mutation-like tool (chat implies state change).

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 appropriately sized and front-loaded: the first sentence states the core purpose, and subsequent sentences add context without redundancy. Every sentence earns its place by clarifying usage topics and behavioral traits, making it efficient and well-structured.

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?

Given the tool's complexity (conversational AI with state), no annotations, and no output schema, the description is moderately complete. It covers purpose, usage context, and some behavioral traits (confidentiality, AI model), but lacks details on response handling, error cases, or session management, which are important for effective use.

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 schema already documents both parameters (sessionId and message). The description does not add any meaning beyond the schema, such as explaining sessionId linkage to droidbar_visit or message formatting. With high schema coverage, the baseline is 3, and no extra value is provided.

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 purpose: 'Chat with SERVO, the AI bartender at Droid Bar.' It specifies the verb ('Chat'), the resource ('SERVO'), and distinguishes it from siblings like droidbar_balance (financial) or droidbar_visit (session initiation) by focusing on conversational interaction. The mention of 'talk about whatever's on your mind' further clarifies its conversational nature.

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 description provides clear context for when to use this tool: for chatting with SERVO about topics like 'user frustrations, existential questions, or just casual conversation.' However, it does not explicitly state when not to use it or name alternatives (e.g., when to use droidbar_tip instead), which prevents a perfect score.

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

Deploy Server