Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_pipelines

Read-onlyIdempotent

Retrieve saved pipeline configurations, optionally filtered by tag or workspace/global scope, and view their names, descriptions, and tags.

Instructions

List all saved pipeline configurations.

Args: tag: Filter by tag (e.g., "sedation"). Empty = show all. scope: Filter by scope: "workspace", "global", or "" (show all).

Returns: Table of saved pipelines with name, scope, description, tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.7
    • addedInput schema / properties / scope / anyOf
      Added value: +[
+  {
+    "default": "",
+    "enum": [
+      "",
+      "workspace",
+      "global"
+    ],
+    "title": "Scope",
+    "type": "string"
+  },
+  {
+    "pattern": "^[ \\t\\r\\n]*(?:|[wW][oO][rR][kK][sS][pP][aA][cC][eE]|[gG][lL][oO][bB][aA][lL])[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / scope / enum
      Removed value: -[
-  "",
-  "workspace",
-  "global"
-]
    • removedInput schema / properties / scope / type
      Removed value: -"string"
  2. Changed4 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / scope / enum
      Added value: +[
+  "",
+  "workspace",
+  "global"
+]
    • addedInput schema / properties / tag / maxLength
      Added value: +100
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_pipelinesOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.5.16

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds the return shape (table with name, scope, description, tags), which is useful behavioral context, but says nothing about ordering, pagination, or limits.

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 one-line purpose followed by a compact Args/Returns block. Every line earns its place; no filler.

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?

With no output schema, the description supplies the return shape, and both param semantics are documented. Only minor gaps remain (no ordering/pagination/limits, no sibling routing).

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 description coverage is 0%, so the description must carry the params—and it does: tag (filter, empty=show all) and scope ('workspace'/'global'/''=show all). This fully maps to both parameters and clarifies the empty-string sentinel semantics the schema only implies via defaults.

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?

Clear specific verb+resource: 'List all saved pipeline configurations.' An agent immediately knows this is a read/list operation. However it does not distinguish itself from siblings like get_pipeline_history, load_pipeline, or list_resolver_presets.

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?

Usage is implied by the filtering args (tag/scope) but there is no explicit statement of when to use this vs load_pipeline, get_pipeline_history, or save_pipeline. No prerequisites noted (e.g., workspace context).

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