Skip to main content
Glama

get-drafts

Retrieve all saved message drafts from Zulip workspaces to review, edit, or send unfinished messages.

Instructions

Retrieve all saved message drafts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:712-734 (registration)
    MCP tool registration for 'get-drafts' including the inline handler that fetches drafts using ZulipClient.getDrafts() and returns formatted MCP response
    server.tool(
      "get-drafts",
      "Retrieve all saved message drafts.",
      {},
      async () => {
        try {
          const result = await zulipClient.getDrafts();
          return createSuccessResponse(JSON.stringify({
            draft_count: result.drafts.length,
            drafts: result.drafts.map(draft => ({
              id: draft.id,
              type: draft.type,
              to: draft.to,
              topic: draft.topic,
              content: draft.content,
              timestamp: new Date(draft.timestamp * 1000).toISOString()
            }))
          }, null, 2));
        } catch (error) {
          return createErrorResponse(`Error getting drafts: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • Core handler in ZulipClient that performs the actual API call to retrieve drafts from Zulip server (/drafts endpoint)
    async getDrafts(): Promise<{ drafts: ZulipDraft[] }> {
      const response = await this.client.get('/drafts');
      return response.data;
    }
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 the tool retrieves drafts but doesn't describe how (e.g., pagination, sorting, filtering), what the return format is, or any limitations (e.g., rate limits, permissions). This is a significant gap for a tool with zero annotation coverage.

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 any fluff. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no wasted verbiage.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'retrieve' entails (e.g., returns a list, JSON structure), any behavioral traits, or usage context. For a tool with no structured data to supplement it, this leaves the agent under-informed about how to effectively use the tool.

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, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details. A baseline of 4 is applied since no parameters exist, and the description doesn't mislead about inputs.

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 action ('retrieve') and resource ('all saved message drafts'), making the purpose specific and understandable. It distinguishes from siblings like 'get-messages' by focusing specifically on drafts rather than all messages. However, it doesn't explicitly contrast with 'edit-draft' or 'create-draft', which slightly limits differentiation.

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 (e.g., needing authentication), when not to use it, or how it compares to similar tools like 'get-messages' (which might include drafts). This leaves the agent with minimal context for selection.

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