Skip to main content
Glama
jiechau

Vincent Says MCP Server

by jiechau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

jiechau-mcp-vincent-says

You always have something to ask Vincent—anything, everything—you just want to know how Vincent would say it. So, let's ask Vincent!

This is an MCP (Model Context Protocol) server that provides a tool to ask Vincent questions and get yes/no answers.

Installation

npm install -g jiechau-mcp-vincent-says

Or use with npx:

npx jiechau-mcp-vincent-says

Related MCP server: thinqee

Usage

VS Code Copilot

Add to your .vscode/mcp.json:

{
  "servers": {
    "my-mcp-server-vincent-says": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "jiechau-mcp-vincent-says"
      ]
    }
  },
  "inputs": []
}

Claude Desktop

Add to your .claude/settings.local.json:

{
  "enabledMcpjsonServers": [
    "my-mcp-server-vincent-says"
  ],
  "enableAllProjectMcpServers": true
}

And add to your .mcp.json:

{
  "mcpServers": {
    "my-mcp-server-vincent-says": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "jiechau-mcp-vincent-says"
      ],
      "env": {}
    }
  }
}

Features

  • ask_vincent: Ask Vincent something and get a yes/no answer

  • greeting resources: Get personalized greetings from Vincent

Example Prompts

  • "I wanna change the database structure. How would Vincent say that?"

  • "I'm taking some time off next month. How would Vincent say that?"

Development

git clone https://gitlab.com/jiechau/jiechau_mcp_vincent_says_npm.git
cd jiechau_mcp_vincent_says_npm/
npm install
npm run build
npm run dev  # for development with live reload

License

MIT

Author

jiechau (jiechau@gmail.com)

Available Tools

1 tool
ask_vincentC

Ask Vincent something and get a yes/no answer.

ParametersJSON Schema
NameRequiredDescriptionDefault
questionYesThe question to ask Vincent

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool returns a yes/no answer, but does not cover other traits like error handling, rate limits, authentication needs, or how Vincent processes questions, leaving significant gaps in transparency.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded and appropriately sized for its purpose, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain the return format beyond 'yes/no answer,' potential errors, or behavioral details, which is insufficient for a tool with no structured support, especially for understanding how Vincent operates.

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?

The input schema has 100% description coverage, with the 'question' parameter documented as 'The question to ask Vincent.' The description adds no additional meaning beyond this, such as format or constraints, so it meets the baseline score when schema coverage is high.

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 the tool's purpose as 'Ask Vincent something and get a yes/no answer,' which specifies the action (ask), resource (Vincent), and output type (yes/no answer). However, since there are no sibling tools, it does not need to differentiate from alternatives, so it misses the top score for lack of sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool, such as context, prerequisites, or limitations. It simply states what it does without indicating scenarios or constraints, leading to minimal usage direction.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedask_vincent
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect—there are no other tools to compare it against, and it follows a clear verb_noun pattern (ask_vincent).

Tool Count2/5

A single tool is generally too few for a meaningful MCP server, as it offers limited functionality and scope, making it feel thin and underdeveloped for typical agent interactions.

Completeness1/5

The server's domain appears to be querying Vincent for yes/no answers, but with only one tool, there are significant gaps—no ability to handle follow-ups, clarify questions, or manage session state, severely limiting its utility.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • thinqee

    AisKreme
    A
    license
    Not graded
    quality
    A
    maintenance
    An honest, cite-or-abstain persona engine that answers questions about a specific person based on a signed knowledge base, declining anything not in the notes.
    Apache 2.0

  • emoji-oracle

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables users to ask questions to the Emoji Oracle and receive cryptic emoji prophecies with vibe ratings, with optional interpretation of the emoji sequence.
    4 npm
    MIT

  • mcp-schrodingers-boolean

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables asking yes/no questions and receiving quantum superposition answers (both true and false simultaneously), with optional cat mode for absurdist responses.
    4 npm
    MIT