Skip to main content
Glama

dismiss

Remove GitHub issues from notifications to reduce notification clutter and focus on active tasks.

Instructions

Dismiss a GitHub issue so it no longer appears in notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull GitHub issue URL to dismiss

Implementation Reference

  • The implementation of the dismiss logic.
    export async function runDismiss(options: { url: string }): Promise<DismissOutput> {
      validateUrl(options.url);
      validateGitHubUrl(options.url, ISSUE_URL_PATTERN, 'issue');
    
      const stateManager = getStateManager();
      const added = stateManager.dismissIssue(options.url, new Date().toISOString());
    
      return { dismissed: added, url: options.url };
    }
  • The tool registration for "dismiss".
    // 18. dismiss — Dismiss an issue
    server.registerTool(
      'dismiss',
      {
        description: 'Dismiss a GitHub issue so it no longer appears in notifications.',
        inputSchema: {
          url: z.string().describe('Full GitHub issue URL to dismiss'),
        },
        annotations: { readOnlyHint: false, destructiveHint: false },
      },
      wrapTool(runDismiss),
    );
Behavior4/5

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

Annotations indicate non-destructive write operation; description adds valuable behavioral specificity that dismissal affects notifications only (not closing/deleting the issue). No contradiction with annotations.

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?

Single sentence, front-loaded with action verb, explains effect without waste. Every clause earns its place.

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

Completeness4/5

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

Sufficient for a single-parameter state-change tool. Safety profile covered by annotations; effect explained. Could note reversibility via 'undismiss' sibling for perfect completeness.

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 coverage is 100% with clear 'url' description; tool description focuses on behavior rather than repeating parameter documentation, which is appropriate at this coverage level.

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?

Clear verb (dismiss) and resource (GitHub issue) with specific outcome (removes from notifications). Could improve by explicitly distinguishing from sibling 'undismiss' or noting reversibility.

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

Usage Guidelines3/5

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

Implies usage context via notification mention, but lacks explicit when-to-use guidance or comparison with alternatives like 'track' or 'undismiss'.

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/costajohnt/oss-autopilot'

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