Skip to main content
Glama
Sign In

Fahi-Videos MCP Server

by io.github.khondokartowsif171
OverviewDiscussionsAdmin

fahi_generate_image

[100% FREE Fallback Included] Generate a 1280x720 HD thumbnail or storyboard image (uses Gemini Image Engine if key is present, or instant 100% free HD visual engine if no key is set).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "fahi_generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesDetailed visual prompt for image generation.
aspectRatioNoOutput aspect ratio (default: 16:9).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses engine fallback behavior, yet says nothing about generation latency, cost, what the return value is (URL, base64, file path), failure modes, or whether output is persisted. For a media-generation tool with zero annotation coverage, this is a significant gap.

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

Conciseness3/5

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

It is a single dense sentence, so it is compact, but the front-loaded '[100% FREE Fallback Included]' tag is promotional noise rather than information an agent needs. The valuable operational details (resolution, engine fallback) are present, but the framing crowds them out.

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?

The tool is simple (2 params, 1 required, no output schema), yet the definition omits the return-value shape, the quality implications of the fallback engine, and whether an API key is required for the Gemini path. With no annotations and no output schema, the description should compensate far more than it does.

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

Parameters2/5

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

Schema coverage is 100% and both parameters are documented including enum values and the 16:9 default, so the schema already does the work. The description adds no parameter meaning: it doesn't clarify whether aspectRatio overrides the claimed 1280x720 size or how much prompt detail is expected. It doesn't even reference the parameters, so it falls below the baseline 3.

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 names a specific verb (generate) and resource (1280x720 HD thumbnail or storyboard image) with an explicit output resolution claim. It distinguishes itself from siblings like fahi_build_ugc_storyboard and the TTS tools by being the image-generation endpoint. The bracketed '[100% FREE Fallback Included]' marketing prefix dilutes the precision, but the core purpose is unambiguous.

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 explains backend routing (Gemini if a key is present, otherwise the free engine) but never states when an agent should pick this tool over fahi_build_ugc_storyboard or fahi_enhance_cinematic_prompt. There are no exclusions, prerequisites, or alternative comparisons; usage must be inferred from the name.

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

All Fahi-Videos MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources