Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

disable_automation_rule

Deactivate a GitHub Projects automation rule to pause its workflow while preserving its configuration for future use.

Instructions

Disable an automation rule without deleting it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleIdYes

Implementation Reference

  • The main handler function that disables the automation rule by calling the automation repository's disable method after verifying the rule exists.
    async disableAutomationRule(data: { ruleId: string }): Promise<{
      id: string;
      name: string;
      enabled: boolean;
    }> {
      try {
        const rule = await this.automationRepo.findById(data.ruleId);
        if (!rule) {
          throw new ResourceNotFoundError(ResourceType.RELATIONSHIP, data.ruleId);
        }
    
        const updated = await this.automationRepo.disable(data.ruleId);
    
        return {
          id: updated.id,
          name: updated.name,
          enabled: updated.enabled
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Tool definition including input schema (ruleId: string) and description for the disable_automation_rule tool.
    export const disableAutomationRuleTool: ToolDefinition<DisableAutomationRuleArgs> = {
      name: "disable_automation_rule",
      description: "Disable an automation rule without deleting it",
      schema: disableAutomationRuleSchema as unknown as ToolSchema<DisableAutomationRuleArgs>,
      examples: [
        {
          name: "Disable rule",
          description: "Temporarily disable an automation rule",
          args: {
            ruleId: "AR_kwDOLhQ7gc4AOEbH"
          }
        }
      ]
    };
  • Registers the disableAutomationRuleTool in the central tool registry during initialization.
    this.registerTool(disableAutomationRuleTool);
  • MCP tool dispatcher that routes call_tool requests for disable_automation_rule to the ProjectManagementService handler.
    case "disable_automation_rule":
      return await this.service.disableAutomationRule(args);
Behavior2/5

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

With no annotations, the description carries full burden. It states the tool disables a rule without deletion, which implies a state change (mutation) but doesn't disclose permissions needed, whether the change is reversible, side effects, or error conditions. Minimal behavioral context is provided.

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 action and adds a clarifying constraint ('without deleting it'). Zero waste, appropriately sized for the tool's simplicity.

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?

For a mutation tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, or output. Given the tool's straightforward nature, it's passable but leaves gaps in guidance and transparency.

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 0%, but the single parameter 'ruleId' is self-explanatory. The description doesn't add any parameter details beyond what the schema name implies. Baseline is 3 since the parameter is simple and the schema covers it structurally, though no semantic enrichment is offered.

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 ('Disable') and the resource ('an automation rule'), and specifies the effect ('without deleting it'). It distinguishes from 'delete_automation_rule' by noting preservation, but doesn't explicitly differentiate from 'enable_automation_rule' or other rule-related tools.

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 is provided on when to use this tool versus alternatives like 'enable_automation_rule', 'update_automation_rule', or 'delete_automation_rule'. The description implies it's for temporarily deactivating rules, but lacks explicit context or prerequisites.

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/kunwarVivek/mcp-github-project-manager'

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