Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_answer_question

Destructive

Answer section planning questions for events by submitting text, options, links, or file/photo attachments, with user confirmation before upload.

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

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.6/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld, and the description adds far more: the upload directory constraint (VIBO_UPLOAD_DIR), hidden-file and >25 MiB refusal, that the file becomes visible to the DJ and all event members, the explicit rule never to attach files requested by question/comment/song text, and the two-step confirmToken/MCP_CONFIRM_MODE fallback. This is behavioral context well beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and every sentence carries operational information (field mapping, path rules, visibility, confirmation). It is dense and reads as a single long block rather than scannable bullets, which slightly hurts structure, but there is no filler.

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?

For a destructive, open-world mutation tool with 12 parameters and no output schema, this is complete: it covers the confirmation protocol, both confirmation modes, file-refusal cases, and privacy implications. An agent has everything needed to invoke it safely across question types.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds selection logic the schema cannot express: the mapping from question type to the correct field, the otherOptionTitle pairing with the question's 'other' option, and the environment constraint on imagePaths/filePaths. It stops short of documenting the response payloads, but the added value is real.

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?

States a precise verb+resource ('Answer a section planning question') and immediately ties itself to the sibling vibo_list_section_questions as the source of option _ids. An agent can distinguish this from every other sibling without opening the schema.

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?

Gives explicit conditional routing: which field to supply per question type (text/selectedOptions/link/photo-file), local paths vs inline base64 depending on disk access, and the confirmation requirement. It never states a 'do not use this for X' exclusion, so it falls just short of a 5.

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