Skip to main content
Glama

get-started

Test connection and get workspace overview to verify functionality and see available streams for orientation and troubleshooting.

Instructions

🚀 START HERE: Test connection and get workspace overview. Use this first to verify everything is working and see available streams. Perfect for orientation and troubleshooting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function executes the 'get-started' tool: tests Zulip connection, fetches user's subscribed streams count and samples, checks recent activity, and returns formatted workspace overview with quick tips.
    async () => {
      try {
        const [streams, recentMessages] = await Promise.all([
          zulipClient.getSubscriptions().catch(() => ({ subscriptions: [] })),
          zulipClient.getMessages({ anchor: "newest", num_before: 3 }).catch(() => ({ messages: [] }))
        ]);
        
        const info = {
          status: "✅ Connected to Zulip",
          your_email: process.env.ZULIP_EMAIL,
          zulip_url: process.env.ZULIP_URL,
          streams_available: streams.subscriptions?.length || 0,
          sample_streams: streams.subscriptions?.slice(0, 5).map((s: any) => s.name) || [],
          recent_activity: recentMessages.messages?.length > 0,
          quick_tips: [
            "Use 'search-users' to find users before sending DMs",
            "Stream names are case-sensitive - use exact names from get-subscribed-streams",
            "Always include 'topic' when sending to streams",
            "For DMs, use actual email addresses (not display names)",
            "Note: 'streams' and 'channels' mean the same thing in Zulip"
          ]
        };
        
        return createSuccessResponse(JSON.stringify(info, null, 2));
      } catch (error) {
        return createErrorResponse(`Connection test failed: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • src/server.ts:370-402 (registration)
    Registration of the 'get-started' tool with server.tool(), including tool name, description, empty input schema ({}), and reference to the handler function.
    server.tool(
      "get-started",
      "🚀 START HERE: Test connection and get workspace overview. Use this first to verify everything is working and see available streams. Perfect for orientation and troubleshooting.",
      {},
      async () => {
        try {
          const [streams, recentMessages] = await Promise.all([
            zulipClient.getSubscriptions().catch(() => ({ subscriptions: [] })),
            zulipClient.getMessages({ anchor: "newest", num_before: 3 }).catch(() => ({ messages: [] }))
          ]);
          
          const info = {
            status: "✅ Connected to Zulip",
            your_email: process.env.ZULIP_EMAIL,
            zulip_url: process.env.ZULIP_URL,
            streams_available: streams.subscriptions?.length || 0,
            sample_streams: streams.subscriptions?.slice(0, 5).map((s: any) => s.name) || [],
            recent_activity: recentMessages.messages?.length > 0,
            quick_tips: [
              "Use 'search-users' to find users before sending DMs",
              "Stream names are case-sensitive - use exact names from get-subscribed-streams",
              "Always include 'topic' when sending to streams",
              "For DMs, use actual email addresses (not display names)",
              "Note: 'streams' and 'channels' mean the same thing in Zulip"
            ]
          };
          
          return createSuccessResponse(JSON.stringify(info, null, 2));
        } catch (error) {
          return createErrorResponse(`Connection test failed: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • General helper function createSuccessResponse used by the get-started handler to format successful responses in MCP format.
    function createSuccessResponse(text: string) {
      return {
        content: [{
          type: "text" as const,
          text
        }]
      };
  • General helper function createErrorResponse used by the get-started handler to format error responses in MCP format.
    function createErrorResponse(message: string) {
      return {
        content: [{
          type: "text" as const,
          text: message
        }],
        isError: true
      };
Behavior4/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 effectively describes the tool's behavior as a connection test and overview provider, including its diagnostic purpose. However, it doesn't specify output format, error handling, or performance characteristics, leaving some behavioral aspects unclear.

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 perfectly front-loaded with the most important information first ('START HERE: Test connection and get workspace overview'), uses only two sentences, and every word earns its place. The emoji adds visual emphasis without sacrificing clarity.

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?

For a zero-parameter diagnostic tool with no annotations and no output schema, the description provides excellent context about purpose and usage. However, without an output schema, it doesn't describe what information the 'workspace overview' or 'available streams' will include, leaving some uncertainty about the return values.

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 baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's purpose and usage 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?

The description clearly states the tool's purpose with specific verbs ('Test connection', 'get workspace overview') and resources ('workspace', 'streams'). It distinguishes from siblings by emphasizing this is a starting point for orientation and troubleshooting, unlike other tools that perform specific operations like sending messages or managing users.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('START HERE', 'Use this first') and provides clear context ('to verify everything is working', 'see available streams', 'Perfect for orientation and troubleshooting'). It distinguishes from alternatives by positioning it as an initial diagnostic tool rather than for ongoing operations.

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

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