Skip to main content
Glama

list_integrations

View available integrations to connect with the PulseMCP Server's note management system for creating, accessing, and summarizing text notes.

Instructions

List all available integrations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'list_integrations' tool: fetches integrations from '/integrations' API endpoint using axios, returns JSON stringified response or error.
    case "list_integrations": {
      try {
        const response =
          await this.axiosInstance.get<ListIntegrationsResponse>(
            "/integrations"
          );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `API Error: ${
                  error.response?.data?.error?.message ?? error.message
                }`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    }
  • TypeScript interface defining the response structure for list_integrations API call.
    interface ListIntegrationsResponse {
      integrations: Array<{
        name: string;
        slug: string;
        url: string;
      }>;
    }
  • src/index.ts:126-133 (registration)
    Tool registration in ListToolsRequestHandler: defines name, description, and empty input schema for list_integrations.
    {
      name: "list_integrations",
      description: "List all available integrations",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'List all available integrations' implies a read operation but doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and front-loads the essential information without unnecessary elaboration.

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?

For a zero-parameter list tool with no output schema, the description provides the minimum viable information about what the tool does. However, it lacks important context about authentication requirements, rate limits, pagination behavior, and output format that would help an agent use it correctly. The absence of annotations increases the need for descriptive completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to add parameter information, and the baseline for this scenario is 4. The description appropriately focuses on the tool's purpose rather than redundant parameter details.

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 available integrations'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'list_servers' - both are list operations but for different resources, so the distinction is implicit rather than explicit.

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. There's no mention of prerequisites, timing considerations, or comparison to the sibling 'list_servers' tool. The agent must infer usage context from 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/orliesaurus/pulsemcp-server'

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