Skip to main content
Glama
Sign In
hydra-mcp

hydra-mcp

by slopwife
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_build

Read-onlyIdempotent

Retrieve a Hydra build’s status, timing, derivation, outputs, products, metrics, and relevant or all build steps to diagnose failures and inspect progress.

Instructions

Get a build: status, timing, derivation, outputs, products, metrics and its build steps.

steps="relevant" (default) lists failed and running steps plus the newest few; "all" lists every step (large for big closures). Failed steps name the dependency behind "dependency failed".

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": {
      "build_id": "<build_id>"
    },
    "name": "get_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNorelevant
build_idYes
instanceNoConfigured Hydra instance; omitted uses the default
recent_stepsNoWith steps="relevant": also the newest N steps

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description adds real value on top: what the default step selection returns, how "all" scales, and the diagnostic behavior where failed steps name the dependency behind "dependency failed". That last detail is non-obvious output semantics an agent could not get from the schema.

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?

Front-loaded with the resource and returned fields, then immediately the parameter that needs explanation. Nearly every sentence carries information; only the line-broken layout makes it slightly more sprawling than needed.

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?

An output schema exists, so return-value detail is optional, yet the description still summarizes content and adds the one behavior (dependency-failure naming) that matters for interpreting results. Missing coverage of steps="none" and no cross-reference to get_build_log are the only residual gaps.

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

Parameters4/5

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

Schema coverage is 50%, so the description must carry weight for the undocumented parameters, and it does: it explains steps="relevant" vs "all" and implies that recent_steps controls the "newest few" shown. The steps="none" value is never explained, leaving one gap in a three-value enum.

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?

States a specific verb and resource and enumerates what the response contains (status, timing, derivation, outputs, products, metrics, steps), which is far more informative than the bare name. It does not explicitly differentiate itself from get_build_log or get_job, so sibling routing is left to inference.

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

Usage Guidelines3/5

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

The description gives clear usage guidance for the steps parameter, including the default and the cost trade-off ("large for big closures"). It says nothing about when to call this instead of get_build_log, get_job, or get_queue, so tool-selection guidance is only implied.

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

Deploy Server

Other Tools