Skip to main content
Glama

relay_skills_list

Discover pre-built workflow skills for common tasks like invoice processing and content pipelines. Filter by category to find reusable patterns with usage examples and context reduction metrics.

Instructions

List available pre-built workflow skills. Skills are reusable patterns for common tasks (invoice processing, content pipelines, etc.). Returns skill names, descriptions, context reduction metrics, and usage examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional: filter by category

Implementation Reference

  • Core handler function that lists available skills, optionally filters by category, sorts them by category and name, and returns the response.
    export async function relaySkillsList(
      input: RelaySkillsListInput
    ): Promise<RelaySkillsListResponse> {
      let skills = [...SKILLS];
    
      // Filter by category if specified
      if (input.category && input.category !== 'all') {
        skills = skills.filter(s => s.category === input.category);
      }
    
      // Sort by category, then by name
      skills.sort((a, b) => {
        if (a.category !== b.category) {
          return a.category.localeCompare(b.category);
        }
        return a.name.localeCompare(b.name);
      });
    
      return { skills };
    }
  • Zod schema for input validation of the relay_skills_list tool.
    export const relaySkillsListSchema = z.object({
      category: z
        .enum(['extraction', 'content', 'integration', 'all'])
        .optional()
        .describe('Optional: filter by category'),
    });
  • MCP tool definition including name, description, and input schema specification used for registration.
    export const relaySkillsListDefinition = {
      name: 'relay_skills_list',
      description:
        'List available pre-built workflow skills. Skills are reusable patterns for common tasks (invoice processing, content pipelines, etc.). Returns skill names, descriptions, context reduction metrics, and usage examples.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          category: {
            type: 'string',
            description: 'Optional: filter by category',
            enum: ['extraction', 'content', 'integration', 'all'],
          },
        },
      },
    };
  • src/server.ts:59-67 (registration)
    The relaySkillsListDefinition is included in the TOOLS array, which is served in response to listTools requests.
    const TOOLS = [
      relayModelsListDefinition,
      relayRunDefinition,
      relayWorkflowRunDefinition,
      relayWorkflowValidateDefinition,
      relaySkillsListDefinition,
      relayRunsListDefinition,
      relayRunGetDefinition,
    ];
  • src/server.ts:129-132 (registration)
    Dispatch logic in the central callTool handler that parses input with the schema and invokes the tool handler.
    case 'relay_skills_list': {
      const parsed = relaySkillsListSchema.parse(args || {});
      result = await relaySkillsList(parsed);
      break;
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that this is a read operation (list/returns) and describes the return format (skill names, descriptions, metrics, examples), which is helpful. However, it doesn't mention potential limitations like pagination, rate limits, authentication requirements, or whether the list is comprehensive versus filtered by default.

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 two sentences that efficiently convey purpose, resource definition, and return details without redundancy. Each sentence adds value: the first defines the action and resource, the second specifies the return format. It's front-loaded and wastes no words.

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?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is reasonably complete. It explains what skills are and what data is returned, which compensates for the lack of output schema. However, for a list operation, it could benefit from mentioning potential behavioral aspects like ordering or default behavior when no category is specified.

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 100%, so the schema fully documents the single optional parameter 'category' with its enum values. The description doesn't add any parameter-specific information beyond what's in the schema, but with only one parameter and high schema coverage, the baseline is 3. The description's explanation of skills provides context that indirectly supports understanding the category filter, warranting a slight bump to 4.

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?

The description clearly states the verb ('List') and resource ('available pre-built workflow skills'), defines what skills are ('reusable patterns for common tasks'), and distinguishes this from siblings like relay_models_list or relay_runs_list by focusing specifically on skills rather than models or runs. It provides specific examples of skill types (invoice processing, content pipelines).

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?

The description implies usage context by explaining what skills are and what information is returned, but it doesn't explicitly state when to use this tool versus alternatives like relay_models_list or relay_workflow_validate. There's no guidance on prerequisites or when-not-to-use scenarios, leaving usage decisions to inference.

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/RelayPlane/mcp-server'

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