Skip to main content
Glama

github_activity_get_thread

Retrieve a specific GitHub notification thread by its ID to view its details.

Instructions

Get a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesthread_id

Implementation Reference

  • The handler function for github_activity_get_thread. Calls githubRequest with GET method to `/notifications/threads/${args.thread_id}`.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/notifications/threads/${args.thread_id}`, undefined, undefined);
    },
  • Input schema for github_activity_get_thread. Takes a required thread_id string parameter.
    inputSchema: z.object({
      thread_id: z.string().describe("thread_id")
    }),
Behavior1/5

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

With no annotations, the description must disclose behavior, but 'Get a thread' provides no information about read-only nature, authentication requirements, side effects, or return data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (three words), but this is under-specification rather than conciseness; it omits essential details.

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

Completeness1/5

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

Given the single parameter and no output schema, the description should explain what a thread is and what the tool returns. It fails to provide any context, making it incomplete.

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?

Schema description coverage is 100% for thread_id, but the description 'thread_id' adds no additional meaning. Baseline 3 is appropriate since the schema already documents the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a thread' is vague; it does not specify what kind of thread (e.g., notification thread, discussion thread) and fails to differentiate from sibling tools like github_activity_get_thread_subscription.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description offers no context for usage decisions.

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

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