Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description bears full responsibility. It discloses the return format ('{ configured: boolean }'), states that the tool never asks for or exposes the key, and implies it performs a read-only check. Fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences, front-loaded with the main purpose. Every sentence adds value: call order, return value, and next steps. No redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with no output schema, the description fully covers what the tool does, what it returns, and how to interpret the result. No gaps in information needed for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description cannot add parameter-level detail beyond what the schema provides. However, it explains the purpose of the tool with no input, which is sufficient. Baseline for 0 parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('Check') and specifies the resource ('whether a Vivideo API key is present'). It uniquely identifies the tool's purpose among siblings, as other tools do not focus on API key presence.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs 'Call this FIRST', providing a strong usage directive. Also describes what to do if the result is false (ask user to add header) and where to obtain the key, guiding appropriate invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose. There is no overlap between tools like check_account and check_configuration, or between the two create video modes. All list tools target different entities, and the remaining tools serve unique roles (estimate credits, get video, wait for video, render preview).
All tool names follow a consistent verb_noun pattern in snake_case, such as check_account, create_auto_video, list_models. This makes it easy to predict tool names and understand their purpose.
With 13 tools, the number is well-scoped for a video generation API. It covers setup, account management, creation (two modes), credit estimation, retrieval, listing of various resources, and video waiting. No tool feels redundant or missing.
The tool surface covers the core workflow well: configuration check, account info, video creation (both auto and manual), credit estimation, retrieval, and listing. However, there are no tools for updating or deleting videos, nor for managing resources beyond listing (e.g., creating avatars or brand kits). These are minor gaps.
