Skip to main content
Glama
soil-dev

capsulemcp

list_track_definitions

List all workflow track definitions to see reusable templates that auto-create tasks at set intervals when applied to projects or opportunities.

Instructions

List workflow track definitions: reusable templates that auto-create tasks at configured intervals when applied to an opportunity or project. Each track includes nested taskDefinitions specifying what to create and when. Use this to understand what automations exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
perPageNoPage size, max 100. Defaults to 100 for reference data.

Implementation Reference

  • The actual handler function for list_track_definitions. Fetches track definitions from Capsule API /trackdefinitions with pagination support.
    export async function listTrackDefinitions(input: z.infer<typeof listTrackDefinitionsSchema>) {
      // Note response key: `trackDefinitions` (camelCase plural). Each entry
      // includes nested taskDefinitions describing the auto-tasks the track
      // creates when applied.
      const { data, nextPage } = await capsuleGet<{ trackDefinitions: unknown[] }>(
        "/trackdefinitions",
        { page: input.page ?? 1, perPage: input.perPage ?? 100 },
      );
      return { ...data, nextPage };
    }
  • Zod schema for list_track_definitions: accepts optional page/perPage pagination fields.
    export const listTrackDefinitionsSchema = z.object({ ...paginationFields });
  • src/server.ts:911-917 (registration)
    Registration of 'list_track_definitions' as an MCP tool in the server, using registerTool helper.
    registerTool(
      server,
      "list_track_definitions",
      "List workflow track definitions: reusable templates that auto-create tasks at configured intervals when applied to an opportunity or project. Each track includes nested taskDefinitions specifying what to create and when. Use this to understand what automations exist.",
      listTrackDefinitionsSchema,
      listTrackDefinitions,
    );
  • src/server.ts:139-140 (registration)
    Import of listTrackDefinitionsSchema and listTrackDefinitions from ./tools/metadata.js.
    listTrackDefinitionsSchema,
    listTrackDefinitions,
  • Shared paginationFields used in the schema definition.
    const paginationFields = {
      page: z.number().int().positive().optional(),
      perPage: z
        .number()
        .int()
        .min(1)
        .max(100)
        .optional()
        .describe("Page size, max 100. Defaults to 100 for reference data."),
    };
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the tool is for listing definitions and mentions nested taskDefinitions, but doesn't mention pagination behavior (though implied by schema). For a read-only list, it's adequate but missing details on ordering or side effects.

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?

Two sentences, no fluff, front-loaded with key information. Every word earns its place.

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?

No output schema, but description mentions nested taskDefinitions. It could explain return format (array of track definitions) or pagination behavior, but for a list tool it's fairly complete. Minor gaps.

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 50% (perPage has description, page does not). Description does not mention parameters. For simple pagination parameters, this is acceptable but not helpful beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states it lists workflow track definitions, which are reusable templates for auto-creating tasks. This distinguishes it from siblings like list_entity_tracks (tracks applied to entities) and show_track (single track detail). The verb 'list' and resource 'track definitions' are specific.

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

Usage Guidelines4/5

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

Provides clear usage context: 'Use this to understand what automations exist.' While it doesn't explicitly exclude alternatives or specify when not to use, the purpose is clear enough for an agent to select this tool for browsing definitions.

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/soil-dev/capsulemcp'

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