Skip to main content
Glama

list_templates

View available business templates with default channels and descriptions to select the right setup for your outreach strategy.

Instructions

List available business templates for the setup_business tool. Shows business types with their default channels and descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the listTemplates method that makes the API request.
    async listTemplates() {
      return this.request('GET', '/api/templates');
    }
  • Registration of the list_templates tool and its handler in the MCP setup.
    {
      name: 'list_templates',
      description:
        'List available business templates for the setup_business tool. Shows business types with their default channels and descriptions.',
      inputSchema: { type: 'object' as const, properties: {} },
      handler: async () => {
        const result = await client.listTemplates();
        return JSON.stringify(result, null, 2);
      },
    },
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 what data is returned ('business types with their default channels'), but omits safety traits (read-only?), pagination behavior, or cache characteristics typical for list operations.

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 efficient sentences with zero waste. First establishes purpose and sibling relationship; second describes return payload. Perfectly front-loaded.

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?

Appropriate for a simple zero-parameter tool. Description compensates for missing output schema by describing what is shown (business types, channels, descriptions), though it could note any pagination limits.

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?

Zero parameters present, which per guidelines establishes a baseline of 4. The description appropriately requires no additional parameter context.

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?

Excellent clarity with specific verb 'List', resource 'business templates', and explicit relationship to sibling tool 'setup_business' that distinguishes its purpose from generic list operations like list_agents.

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?

Provides implied context that these templates are for setup_business, but lacks explicit guidance on when to call this (before vs during setup), prerequisites, or when to avoid using templates.

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/diegotorreslopez81/swarmix-mcp'

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