Skip to main content
Glama

list_task_definitions

Retrieve metadata for all tasks registered in Conductor to manage and troubleshoot workflow executions.

Instructions

List all registered task definitions. Returns metadata about all tasks registered in Conductor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessNoFilter by access type (READ or CREATE)

Implementation Reference

  • Handler that lists all registered task definitions from Conductor by calling the /metadata/taskdefs API endpoint, optionally filtered by 'access' parameter (READ or CREATE). Returns JSON response as text.
    case "list_task_definitions": {
      const params: any = {};
      
      if ((args as any).access) params.access = (args as any).access;
      
      const response = await conductorClient.get("/metadata/taskdefs", { params });
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Tool schema defining the name, description, and input schema for list_task_definitions. Input optionally accepts 'access' filter.
    {
      name: "list_task_definitions",
      description:
        "List all registered task definitions. Returns metadata about all tasks registered in Conductor.",
      inputSchema: {
        type: "object",
        properties: {
          access: {
            type: "string",
            description: "Filter by access type (READ or CREATE)",
            enum: ["READ", "CREATE"],
          },
        },
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states it returns metadata without detailing format, pagination, or sorting. It doesn't cover behavioral traits like permissions needed, rate limits, or whether it's a read-only operation, which is a significant gap for a listing tool.

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?

The description is a single, efficient sentence that front-loads the core action and purpose. Every word earns its place with no redundancy or waste, making it appropriately sized for a simple tool.

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?

Given no annotations and no output schema, the description is incomplete for a listing tool. It lacks details on return format, pagination, or error handling, which are crucial for agent usage. The simplicity of the tool partially mitigates this, but more context is needed.

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%, so the schema fully documents the single parameter 'access' with its enum values. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high coverage.

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 ('List') and resource ('all registered task definitions'), specifying it returns metadata about tasks registered in Conductor. It distinguishes from siblings like 'get_task_definition' by implying a bulk listing, but doesn't explicitly differentiate from 'list_workflow_definitions' or 'list_workflows'.

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 is provided on when to use this tool versus alternatives like 'get_task_definition' for a single task or 'list_workflow_definitions' for workflows. The description lacks explicit when/when-not instructions or prerequisites, leaving usage context implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/opensensor/conductor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server