Skip to main content
Glama
robertn702

Sunsama MCP Server

get-streams

Retrieve available project streams (called channels in Sunsama) to organize and categorize tasks within your workspace.

Instructions

Get streams for the user's group (streams are called 'channels' in the Sunsama UI)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler for the 'get-streams' tool. Uses withTransportClient wrapper to fetch streams via context.client.getStreamsByGroupId() and formats response as TSV.
    export const getStreamsTool = withTransportClient({
      name: "get-streams",
      description:
        "Get streams for the user's group (streams are called 'channels' in the Sunsama UI)",
      parameters: getStreamsSchema,
      execute: async (_args: GetStreamsInput, context: ToolContext) => {
        const streams = await context.client.getStreamsByGroupId();
    
        return formatTsvResponse(streams);
      },
    });
  • Zod input schema for 'get-streams' tool, defining no required parameters.
    export const getStreamsSchema = z.object({});
  • src/main.ts:33-44 (registration)
    Server-level registration of all tools including 'get-streams' by calling registerTool on McpServer instance for each tool in allTools.
    allTools.forEach((tool) => {
      server.registerTool(
        tool.name,
        {
          description: tool.description,
          inputSchema: "shape" in tool.parameters
            ? tool.parameters.shape
            : tool.parameters,
        },
        tool.execute,
      );
    });
  • src/tools/index.ts:3-9 (registration)
    Aggregates tool lists from various modules, including streamTools containing 'get-streams', into the allTools export used for server registration.
    import { streamTools } from "./stream-tools.js";
    
    export const allTools = [
      ...userTools,
      ...taskTools,
      ...streamTools,
    ];
  • Local registration/export of the getStreamsTool in an array for inclusion in global tools list.
    export const streamTools = [getStreamsTool];
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 this is a 'Get' operation, implying read-only behavior, but doesn't clarify permissions, rate limits, pagination, or what 'user's group' entails. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose ('Get streams for the user's group') and adds clarifying context without waste. Every word earns its place, making it appropriately sized and well-structured.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains what the tool does and provides UI terminology, but lacks details on behavior, usage context, or output format. This meets the minimum viable threshold but doesn't fully compensate for the absence of annotations or output schema.

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's no need for parameter details in the description. The description appropriately doesn't mention parameters, which aligns with the schema. A baseline of 4 is given since no parameters exist, and the description doesn't add unnecessary information.

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 tool's purpose: 'Get streams for the user's group', which is a specific verb+resource combination. It also provides helpful context by explaining that 'streams are called 'channels' in the Sunsama UI', which aids understanding. However, it doesn't explicitly distinguish this tool from its sibling tools (like get-tasks-backlog or get-tasks-by-day), which would require a 5.

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, timing, or comparisons to sibling tools (e.g., when to use get-streams vs. get-tasks-by-day). The context about 'user's group' and UI terminology is useful but doesn't constitute usage guidelines.

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/robertn702/mcp-sunsama'

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