Skip to main content
Glama

github_activity_get_repo_subscription

Check your subscription status for any GitHub repository. Provide the owner and repo name to view subscription details.

Instructions

Get a repository subscription

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesowner
repoYesrepo

Implementation Reference

  • The handler function that executes the tool logic for github_activity_get_repo_subscription. It makes a GET request to /repos/{owner}/{repo}/subscription.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/repos/${args.owner}/${args.repo}/subscription`, undefined, undefined);
    },
  • Input schema for the tool, requiring 'owner' and 'repo' string parameters.
    inputSchema: z.object({
      owner: z.string().describe("owner"),
      repo: z.string().describe("repo")
    }),
  • The tool definition object with name 'github_activity_get_repo_subscription', description, inputSchema, and handler — part of the activityTools array.
    {
      name: "github_activity_get_repo_subscription",
      description: "Get a repository subscription",
      inputSchema: z.object({
        owner: z.string().describe("owner"),
        repo: z.string().describe("repo")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/repos/${args.owner}/${args.repo}/subscription`, undefined, undefined);
      },
    },
  • src/index.ts:110-130 (registration)
    Tools are registered via server.tool() in a loop. The tool's name, description, inputSchema, and handler are passed to the MCP server.
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
    }
  • src/index.ts:57-57 (registration)
    The activityTools array (containing the tool) is imported and placed in the 'activity' category for registration.
    { category: "activity", tools: activityTools },
Behavior2/5

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

Description only indicates a read operation but provides no details on what the subscription entails, what happens if not subscribed, or any side effects. With no annotations, 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.

Conciseness4/5

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

Single sentence is concise and front-loaded, but lacks structure. Every word earns its place, but more detail could be added without losing conciseness.

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?

No output schema or annotations. Description does not explain the return format, what a subscription is, or any preconditions. Incomplete for a tool with no additional metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter descriptions are minimal ('owner', 'repo') and do not add meaning beyond the names. Schema coverage is 100% but provides no additional context for usage.

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?

Description clearly states verb 'Get' and resource 'repository subscription', distinguishing it from sibling tools like set or delete. It is specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives like set or delete subscription. Does not mention prerequisites or context such as authentication requirements.

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