Vibie MCP

vibie_detect_hosts

Detect which video editors—FilmCraft, Adobe Premiere Pro, or both—are currently online and reachable so AI assistants can route editing tasks to an available host.

Instructions

Detects which video editors (FilmCraft, Adobe Premiere Pro, or both) are currently online and reachable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vibie_detect_hosts"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the key trait: this is a live/current reachability check ('currently online and reachable'), not a static config read. It omits whether the probe blocks or times out, what happens when nothing is reachable, and what the result looks like.

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?

A single sentence with no filler, and the operative information (which editors, and that they must be online) is front-loaded. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a zero-parameter discovery tool with no output schema, the description covers the essentials, including the enumerated editor set that implicitly defines the result shape. It stops just short of stating the return form (list of found hosts) or the empty-result behavior.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and no schema gap to compensate for. The baseline of 4 applies.

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?

Names a specific verb (detects) and resource (video editors) and enumerates the possible subjects (FilmCraft, Adobe Premiere Pro, or both), so an agent knows exactly what the call answers. It does not name vibie_set_target_host or otherwise differentiate itself from that sibling, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step that precedes vibie_set_target_host, but the description never says 'call this first' or gives any condition for choosing it over configuring a target directly. No exclusions or failure-handling guidance are offered.

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