Skip to main content
Glama
Sign In
hydra-mcp

hydra-mcp

by slopwife
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_projects

Read-onlyIdempotent

Retrieves Hydra projects and associated jobsets, optionally from a configured instance, to help agents inspect project structure.

Instructions

List the projects of a Hydra instance with their jobsets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoConfigured Hydra instance; omitted uses the default

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no repetition. The description adds that jobsets are bundled into the result, which is genuine extra information, but says nothing about ordering, pagination, or failure behavior for an unknown instance.

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?

One short sentence that front-loads the action and resource with zero padding. Nothing could be removed without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations are rich, so the description needn't explain return values or safety. Still, for a listing tool with an open-world instance selector, it gives no hint about result scope or how the instance affects what is returned.

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 coverage is 100% and the single `instance` parameter is already documented as 'omitted uses the default'. The description adds nothing about the parameter, so the baseline of 3 applies.

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 ('List the projects of a Hydra instance') and adds a useful scope note that jobsets are included. It is distinguishable from get_project (single project) by the plural 'projects', though it never explicitly contrasts with siblings.

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

Usage Guidelines2/5

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

No statement of when to use this versus get_project, list_instances, or search. The agent must infer that this is the enumeration entry point and that list_instances may be needed first to obtain a valid instance name.

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