Skip to main content
Glama
mcollina

GitHub Notifications MCP Server

get-thread

Retrieve detailed information about a specific GitHub notification thread by providing its thread ID to manage notifications effectively.

Instructions

Get information about a GitHub notification thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesThe ID of the notification thread to retrieve

Implementation Reference

  • The getThreadHandler function implements the core logic of the 'get-thread' tool: fetches the GitHub notification thread by ID, formats it, and returns the response or error.
    export async function getThreadHandler(args: z.infer<typeof getThreadSchema>) {
      try {
        // Make request to GitHub API
        const thread = await githubGet<NotificationResponse>(`/notifications/threads/${args.thread_id}`);
    
        // Format the thread for better readability
        const formattedThread = formatNotification(thread);
    
        return {
          content: [{
            type: "text",
            text: `Thread details:\n\n${formattedThread}`
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{
            type: "text",
            text: formatError(`Failed to fetch thread ${args.thread_id}`, error)
          }]
        };
      }
    }
  • Zod schema defining the input parameter 'thread_id' for the 'get-thread' tool.
    export const getThreadSchema = z.object({
      thread_id: z.string().describe("The ID of the notification thread to retrieve")
    });
  • The registerGetThreadTool function registers the 'get-thread' tool with the MCP server, specifying name, description, input schema, and handler.
    export function registerGetThreadTool(server: any) {
      server.tool(
        "get-thread",
        "Get information about a GitHub notification thread",
        getThreadSchema.shape,
        getThreadHandler
      );
    }
  • src/server.ts:40-40 (registration)
    Invocation of the registerGetThreadTool function during server initialization to register the tool.
    registerGetThreadTool(server);
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 read operation ('Get information'), which implies it's non-destructive, but doesn't cover other important aspects like authentication requirements, rate limits, error handling, or what specific information is returned (e.g., thread details, status). For a tool with zero annotation coverage, this is insufficient.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information, making it easy to parse quickly.

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 information is returned (e.g., thread content, metadata, or subscription status), which is critical for a retrieval tool. While the schema covers the input parameter well, the overall context for using the tool effectively is lacking.

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 input schema has 100% description coverage, with the single parameter 'thread_id' clearly documented in the schema. The description doesn't add any additional parameter context beyond what's in the schema (e.g., format examples, where to find thread IDs, or validation rules), so it meets the baseline of 3 where the schema does the heavy lifting.

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 resource ('information about a GitHub notification thread'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar siblings like 'list-notifications' or 'list-repo-notifications', which also retrieve notification-related information but with different scopes.

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 a specific thread ID), exclusions, or how it differs from sibling tools like 'list-notifications' (which lists multiple notifications) or 'mark-thread-read' (which modifies thread state).

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/mcollina/mcp-github-notifications'

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