Skip to main content
Glama

maxion-mcp-gateway

by io.github.aruuhii2yo

Generate AI Video or Image

media_lineage0_generate

4K AI video via Amazon Nova Reel 1.1 or commercial-ready images via Nova Canvas. Polls until synthesis completes and returns a presigned download URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesNatural-language description of the desired video or image content.
durationNoRequired for media_type='video': the purchased credit's duration in seconds. Must match the duration passed to billing_purchase.
media_typeYesOutput format: 'video' for 4K Nova Reel 1.1 synthesis, 'image' for Nova Canvas commercial-grade image.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoGenerated media URL or synthesis job status.

TDQS

A4.2/5.0
Behavior4/5

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

Description adds valuable behavioral context beyond the sparse annotations: it polls until synthesis completes and returns a presigned download URL. It does not mention billing prerequisites or failure behavior, but the annotations (readOnlyHint=false, idempotentHint=false) align with a creation operation and no contradiction exists.

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 22-word sentence front-loads the purpose and includes the key behavioral trait (polling) and output form (presigned URL). No filler or redundancy.

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?

The description covers purpose, output modalities, and return behavior; output schema presumably documents the presigned URL. The billing dependency is referenced in the schema's duration description, so the description is mostly complete, though it could ideally mention that a purchased credit is required.

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

Parameters3/5

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

Schema description coverage is 100% with clear per-parameter details (media_type enum, prompt semantics, duration tied to billing_purchase). The description adds no additional parameter-level meaning, so baseline 3 is appropriate.

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?

Description explicitly states the tool generates 4K AI video via Amazon Nova Reel 1.1 or commercial-ready images via Nova Canvas, with a distinct verb and resource. It clearly differentiates from sibling tools like archive and status by describing a creation workflow.

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 makes the tool's role as the media generation entry point obvious among storage/security/billing siblings, and mentions polling behavior that sets expectations for when to use it. However, it does not explicitly name alternatives or state exclusions for non-video/image workloads.

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

All maxion-mcp-gateway toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Each tool has a distinct name and purpose within its domain (billing, engine, media, security, storage, gateway). While there is some semantic overlap (e.g., engine_maxion_status vs. engine_maxion_diagnostics), the specific functions are clear enough to avoid misselection.

Naming Consistency3/5

Naming patterns are inconsistent: some tools use domain_entity_action (engine_maxion_activate), others use domain_action (billing_activate), and one uses just domain_status (gateway_status). The inclusion of 'lineage0' and '0' suffixes adds further irregularity.

Tool Count3/5

19 tools is on the higher end but justifiable for a multi-service gateway. However, several tools are stubs (NOT IMPLEMENTED), and there are multiple status/diagnostic tools per domain, which makes the set feel padded rather than tightly scoped.

Completeness2/5

The tool surface is incomplete in several areas: security lacks functional quarantine and logging, engine lacks a working deactivate, and there is no way to manage billing subscriptions or view media history beyond a simple archive list. The presence of explicitly NOT IMPLEMENTED tools highlights these gaps.

Resources