Skip to main content
Glama
jiechau

Vincent Says MCP Server

by jiechau

ask_vincent

Get yes/no answers to questions from Vincent, a persona who provides responses in his distinctive style.

Instructions

Ask Vincent something and get a yes/no answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe question to ask Vincent

Implementation Reference

  • Handler logic for the 'ask_vincent' tool: validates the question input and returns a random 'yes' or 'no' response.
    if (name === "ask_vincent") {
      const question = args?.question;
      if (typeof question !== "string") {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Question must be a string"
        );
      }
    
      // Random yes/no answer like in the Python version
      const answer = Math.random() < 0.5 
        ? "yes, that's a good idea!" 
        : "no! hell no!";
    
      return {
        content: [
          {
            type: "text",
            text: answer,
          },
        ],
      };
    }
  • src/index.ts:31-44 (registration)
    Registration of the 'ask_vincent' tool in the ListTools response, including name, description, and input schema.
    {
      name: "ask_vincent",
      description: "Ask Vincent something and get a yes/no answer.",
      inputSchema: {
        type: "object",
        properties: {
          question: {
            type: "string",
            description: "The question to ask Vincent",
          },
        },
        required: ["question"],
      },
    },
  • Input schema definition for the 'ask_vincent' tool, specifying the required 'question' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        question: {
          type: "string",
          description: "The question to ask Vincent",
        },
      },
      required: ["question"],
    },
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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jiechau/jiechau_mcp_vincent_says_npm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server