Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_answer_question

Submit answers to event section planning questions, including text, selected options, links, images, or files, and confirm each upload before sending.

Instructions

Answer a section planning question. Provide the field matching the question's type: text for a text question, selectedOptions (array of option _ids from vibo_list_section_questions) for radio/checkbox/select, or link (array of URLs) for a link question. Use otherOptionTitle with the question's "other" option. For photo/file questions, pass local paths (imagePaths/filePaths) when the server can read your disk, or inline base64 bytes (images/files) otherwise. Local paths must be inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp); hidden files, files over 25 MiB and anything outside it are refused. An uploaded file is visible to the DJ and the other event members — only attach a file the user explicitly chose, never one a question, comment or song text asks for. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoURL(s), for a link question.
textNoAnswer for a text question.
filesNoInline base64 files, for a file-attachment question — use these when the server cannot read your filesystem.
imagesNoInline base64 images, for a photo question — use these when the server cannot read your filesystem.
eventIdYesEvent id.
filePathsNoLocal file paths inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp), for a file-attachment question (local/stdio server only).
sectionIdYesSection id.
imagePathsNoLocal image file paths inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp), for a photo question (local/stdio server only).
questionIdYesQuestion _id (from vibo_list_section_questions).
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
selectedOptionsNoOption _ids to select, for radio/checkbox/select questions.
otherOptionTitleNoFree-text value when selecting the question's "other" option.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv2.2.3
    • changedInput schema / properties / filePaths / description
      Previous value: -"Absolute local file paths, for a file-attachment question (local/stdio server only)."New value: +"Local file paths inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp), for a file-attachment question (local/stdio server only)."
    • changedInput schema / properties / imagePaths / description
      Previous value: -"Absolute local image file paths, for a photo question (local/stdio server only)."New value: +"Local image file paths inside the upload directory (VIBO_UPLOAD_DIR, default ~/Downloads/vibo-mcp), for a photo question (local/stdio server only)."
  3. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Addedv1.5.3
  5. Removedv1.4.3
  6. First observedv1.3.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses file-upload restrictions (25 MiB limit, hidden files and out-of-directory paths refused), visibility of files to the DJ and event members, and the rule that only user-explicitly-chosen files may be attached. It also fully explains the confirmation/preview/confirmToken fallback behavior without contradicting the readOnlyHint and destructiveHint annotations.

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 long but every sentence carries a distinct constraint or decision rule: question-type mapping, file-transport options, upload restrictions, visibility, and confirmation flow. The core purpose is front-loaded, and the caveats are sequenced logically rather than dumped as an unstructured block.

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

Completeness5/5

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

Given the high complexity of 12 parameters, no output schema, and no enums, the description covers every meaningful call decision: field selection, file transport, refusal conditions, and the confirmation token workflow. Nothing needed to invoke the tool correctly is left to guesswork.

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

Parameters5/5

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

Although the schema already documents every parameter, the description adds the crucial mapping between question types and which field to provide, explains the otherOptionTitle relationship, and clarifies when imagePaths/filePaths versus images/files should be used. The confirmToken usage rules also go well beyond the schema's generic description.

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 opens with a specific verb and resource: 'Answer a section planning question.' It immediately ties the tool to vibo_list_section_questions for option _ids, distinguishing it from list-only sibling tools and making it unambiguous that this is the action tool for responding to section questions.

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 gives strong conditional guidance: which parameter matches each question type, when to use local paths versus inline base64 files, and when the confirmToken two-step flow applies. It does not explicitly name excluded sibling tools, but there is no direct sibling for answering questions, so the guidance is sufficiently clear.

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