Skip to main content
Glama
Bedolla

EnriVision

by Bedolla
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

analyze_media

Upload local media files for server-side extraction and analysis, handling large PDFs, videos, audio, and complex formats beyond client capabilities.

Instructions

Upload and analyze a local file via EnriProxy (server-side extraction + model analysis).

When to use:

  • Large PDFs (many pages) or scanned PDFs where client-side Read may truncate or miss content.

  • Video/audio or other binary media your client cannot Read.

  • Audio files in common formats (mp3, wav, flac, m4a, aac, ogg/oga, opus, wma, weba, mka, aiff/aif/aifc, caf, m4b/m4r, mp1/mp2/mpa/mpga).

  • HEIC/AVIF/TIFF/APNG/SVG/Office docs when your client Read is unreliable.

  • Very large files where resumable uploads are required (up to 4GB).

  • Large PDFs/videos: set analysis_mode to 'multipass' for better coverage (auto prefers multipass for PDFs > 20 pages).

  • For time-specific video questions (e.g., "what happens at 12:34?"), set video.clip_start_seconds and video.clip_duration_seconds.

Rules:

  • Use path for one file, or paths for multiple images (UI screenshots/photo sets).

  • path/paths are absolute paths on the machine running this MCP server (the client).

  • Requires a valid EnriProxy API key (env ENRIPROXY_API_KEY, sent as Authorization: Bearer ...).

  • Prefer the client's native Read tool only for small/simple text/PDF/common images when it works; prefer this tool for large PDFs.

  • Answer strictly from the tool output; if frames/transcript are missing, say so.

  • Video: frames + transcript belong to the SAME video timeline (not unrelated images).

  • Animated GIF/WebP/APNG/SVG inputs are converted into representative key frames.

  • Set language (e.g., 'es') to match the user request and avoid language drift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoAbsolute path to a local file on the machine running the MCP server (e.g., C:\\Users\\User\\Downloads\\video.mp4).
pathsNoAbsolute paths to multiple local image files (UI screenshots/photo sets). When provided, EnriVision uploads a single media-set archive for server-side batching + reduce.
contextNoOptional analysis hint: ui, diagram, chart, error, code, meeting, tutorial, photo. Leave empty for auto-detection.
questionNoOptional explicit question to answer about the file.
languageNoPreferred response language code (ISO 639-1), e.g. 'es', 'en'.
max_framesNoOptional max frames for videos (1-20) in single-pass mode. For targeted timestamps, prefer video.clip_start_seconds + video.clip_duration_seconds. For multipass, use video.max_frames_per_segment.
transcribeNoOptional override to enable/disable audio transcription for videos.
transcription_languageNoOptional Whisper language hint for audio/video transcription (e.g., 'auto', 'es', 'en').
analysis_modeNoOptional analysis mode selector: auto, single, or multipass.
videoNoOptional video multipass tuning. Used only when analyzing videos.
documentNoOptional document multipass tuning (PDF).
audioNoOptional audio multipass tuning (used only when analyzing audio files).
imagesNoOptional image-set multipass tuning (used only with `paths`).

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden of behavior disclosure. It explains the tool performs server-side extraction and analysis, requires an EnriProxy API key, handles various media types with conversion (animated GIF/WebP to key frames), and specifies that output should be strictly from the tool output with missing frames/transcript noted. It also states the tool is for analysis, implying no destructive side effects on the file.

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?

The description is lengthy but well-structured with clear headings (When to use, Rules) and bullet points. It front-loads the core purpose and then provides specific guidance. While every sentence serves a purpose, some redundancy exists (e.g., repeated mentions of large PDFs). Nonetheless, it is appropriately sized for the tool's complexity.

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?

Given the tool's complexity (13 parameters, multiple media types, no output schema), the description is remarkably complete. It covers when to use, constraints (API key, absolute paths), specific parameter usage for different scenarios, and expected output behavior. It also explains the absence of frames/transcript if missing. No gaps are apparent.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant semantic value beyond parameter definitions. It explains when to use `path` vs `paths`, how to use video clip parameters for time-specific questions, and the interplay between `max_frames`, `analysis_mode`, and multipass tuning. This enriches the schema's minimal descriptions, making parameters much more understandable in context.

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?

The description clearly states it uploads and analyzes local files via EnriProxy for server-side extraction and model analysis. It lists many specific use cases (large PDFs, videos, audio, etc.) and distinguishes from a client-side Read tool, making the purpose highly specific and actionable.

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

Usage Guidelines5/5

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

The 'When to use' section explicitly lists scenarios where this tool is preferred over client Read, such as large PDFs, videos, audio, and images with unreliable client reading. It also provides rules like preferring client Read for small/simple files, and gives detailed guidance for video time-specific questions and multipass mode. This is comprehensive and clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bedolla/EnriVision'

If you have feedback or need assistance with the MCP directory API, please join our Discord server