versionator-mcp

get_nfcore_subworkflow

Get the latest version of an nf-core subworkflow by specifying its name. Access current subworkflow metadata.

Instructions

Get the latest version of an nf-core subworkflow.

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": {
      "subworkflow_name": "<subworkflow_name>"
    },
    "name": "get_nfcore_subworkflow"
  }
}

Input Schema

Name	Required	Description	Default
`subworkflow_name`	Yes	The subworkflow name (e.g., "bam_sort_stats_samtools")

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description only states 'get the latest version'. It does not disclose behavioral traits such as read-only nature, response format, or any side effects. Given the lack of annotations, the description should carry more behavioral context.

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 a single, concise sentence with no wasted words. It is front-loaded with the main action and resource.

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

Completeness2/5

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

While the tool has an output schema and a single parameter, the description lacks context about usage, prerequisites, and differentiation from siblings. Given the low complexity, it is minimally complete but not sufficiently helpful for an agent to choose correctly among many similar tools.

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 description coverage is 100% for the single parameter, which already includes an example. The tool description does not add any additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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?

The description clearly states the verb 'get' and the resource 'latest version of an nf-core subworkflow'. It distinguishes from siblings like get_nfcore_module by specifying 'subworkflow', but does not clarify the difference between subworkflow and module.

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 guidance on when to use this tool versus alternatives. The description does not provide context for selecting this over similar get_* tools like get_nfcore_module or get_nextflow_pipeline.

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