Skip to main content
Glama

list_connections

Retrieve all configured app connections from the Automatisch workflow automation platform, with optional filtering by specific applications.

Instructions

List all app connections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appKeyNoFilter by specific app

Implementation Reference

  • Registration of the 'list_connections' tool including name, description, and input schema in the ListToolsRequestHandler response.
    {
      name: "list_connections",
      description: "List all app connections",
      inputSchema: {
        type: "object",
        properties: {
          appKey: {
            type: "string",
            description: "Filter by specific app"
          }
        }
      }
    },
  • The CallToolRequestHandler case for 'list_connections' that invokes the API helper and formats the response as JSON text content.
    case "list_connections":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.listConnections(args), null, 2)
          }
        ]
      };
  • API helper method stub for listConnections, intended to contain the core logic for listing connections (currently unimplemented).
    listConnections: async function(args: any = {}) {
      // ... copy listConnections logic from index.ts ...
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List all app connections' but doesn't describe the return format (e.g., list of objects, pagination), permissions required, or any rate limits. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with zero waste: 'List all app connections'. It's front-loaded and appropriately sized for a simple tool, making it easy to parse without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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), the description is minimally complete but lacks depth. It covers the basic purpose but doesn't address behavioral aspects like return format or usage context, which are important for an agent to invoke it correctly without annotations or output schema.

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?

The input schema has 100% description coverage, with the single parameter 'appKey' documented as 'Filter by specific app'. The description doesn't add any meaning beyond this, such as examples of app keys or how filtering works. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 app connections'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'get_available_apps' or 'create_connection', which would require more specificity about what distinguishes listing connections from other operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing existing connections, or compare it to siblings like 'get_available_apps' (which might list apps vs. connections). Without this context, usage is implied but not explicit.

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

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