Skip to main content
Glama
j-rdel

pipeline_watch

by j-rdel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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_workflow_runA

Fetch a single GitHub Actions workflow run.

Args:
    repo: "owner/name", e.g. "j-rdel/pipeline_watch". Ignored in fixture mode.
    run_id: run identifier. In fixture mode, must match a file in
            fixtures/workflow_runs/{run_id}.json.

Returns:
    Subset of the GitHub workflow_run payload (id, name, head_branch,
    head_sha, event, status, conclusion, run_started_at, repository,
    jobs_url).
get_job_logsA

Fetch the raw log text for a single job of a workflow run.

Args:
    repo: "owner/name". Ignored in fixture mode.
    run_id: run identifier (needed for the fixture backend).
    job_id: job identifier.

Returns:
    Raw log text. May be truncated by the caller downstream.

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

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target entirely distinct resources: workflow run metadata versus job log text. There is no overlap or ambiguity in their purposes.

Naming Consistency5/5

Both tools follow the same get_<resource> snake_case pattern, with clear nouns (workflow_run, job_logs). The naming is perfectly consistent.

Tool Count3/5

With only two tools, the server feels thin but not unreasonable for a narrowly focused watch-only utility. It is at the borderline of acceptable scope.

Completeness2/5

The server can fetch a single run by ID and its job logs, but there is no way to list workflow runs or jobs. An agent would need to already know the run_id, making discovery impossible and creating a significant dead end.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources