Skip to main content
Glama
rohitreddynagareddy

encoding-devops

by rohitreddynagareddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_job_by_nameC

Get details of an encoding job by its name

get_job_tasks_by_idC

Get tasks for a specific job by its ID

get_clientsB

Get list of all clients

is_cluster_busyB

Check if the encoding cluster is busy (has jobs in progress)

get_latest_jobsB
Get the most recent encoding jobs

Args:
    limit: Number of jobs to return (default: 3, max: 10)

Returns:
    String representation of the latest jobs
search_movieC
Search for a movie by title

Args:
    title: Movie title to search for

Returns:
    String representation of the search results
get_movie_detailsB
Get detailed information about a movie by its IMDB ID

Args:
    imdb_id: IMDB ID of the movie (e.g., 'tt0111161')

Returns:
    String representation of the movie details
open_emailA
Opens the default email client with your message ready to go

Args:
    body: What you want to say in the email
    to: Who to send it to (optional)
    subject: Email subject line (optional)
    cc: CC recipients (optional)
    bcc: BCC recipients (optional)
    ctx: MCP context

Returns:
    str: Quick status message so you know it worked

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

B3.3/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target clear, distinct resources (clients, cluster status, movie search, email). The three job-related tools (get_job_by_name, get_job_tasks_by_id, get_latest_jobs) share a resource but differ in intent, so only minor confusion is possible.

Naming Consistency4/5

Names follow a consistent snake_case verb_noun pattern (get_job_by_name, get_movie_details, search_movie). The is_cluster_busy predicate is a reasonable deviation for a boolean check rather than a true inconsistency.

Tool Count5/5

Eight tools is well-scoped for this domain, with each covering a distinct query. No redundant or filler tools pad the surface.

Completeness3/5

The surface is read-only: it exposes job lookups, cluster status, and movie info but no submit/create/cancel/retry job operations, which are core to an encoding-ops workflow. Client and email handling are present but job lifecycle coverage is one-sided.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources