Skip to main content
Glama

get_available_apps

Retrieve available apps and their capabilities from the Automatisch workflow automation platform to identify integration options for building automated workflows.

Instructions

Get list of available apps and their capabilities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by app category

Implementation Reference

  • The execution handler for the 'get_available_apps' tool. It calls the API helper main.api.getAvailableApps(args) and formats the result as JSON text content.
    case "get_available_apps":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.getAvailableApps(args), null, 2)
          }
        ]
      };
  • Registration of the 'get_available_apps' tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_available_apps",
      description: "Get list of available apps and their capabilities",
      inputSchema: {
        type: "object",
        properties: {
          category: {
            type: "string",
            description: "Filter by app category"
          }
        }
      }
    },
  • Input schema definition for the 'get_available_apps' tool.
    inputSchema: {
      type: "object",
      properties: {
        category: {
          type: "string",
          description: "Filter by app category"
        }
      }
    }
  • API helper function getAvailableApps that implements the core logic for retrieving available apps (currently a stub). Called by the tool handler.
    getAvailableApps: async function(args: any = {}) {
      // ... copy getAvailableApps logic from index.ts ...
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't add context about traits like whether it's read-only, requires permissions, has rate limits, or what the return format looks like. This leaves significant gaps for a tool that presumably lists resources.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits and usage context, making it incomplete for optimal agent decision-making without additional inference.

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 schema description coverage is 100%, so the input schema fully documents the 'category' parameter. The description doesn't add any meaning beyond this, such as examples of categories or how filtering works, but it doesn't need to compensate for gaps, resulting in a baseline score.

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 'Get' and the resource 'list of available apps and their capabilities', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_connections' or 'list_workflows' by specifying what makes 'apps' distinct, which prevents a perfect score.

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 like 'list_connections' or 'list_workflows'. It lacks context about prerequisites, such as whether authentication is needed, or exclusions, leaving the agent to infer usage based on the tool name alone.

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