Skip to main content
Glama
costajohnt

oss-autopilot

by costajohnt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

undismiss

Re-enable notifications for a previously dismissed GitHub issue by providing its URL, restoring issue tracking and alerts.

Instructions

Undismiss a previously dismissed issue, re-enabling notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull GitHub issue URL to undismiss

Implementation Reference

  • packages/core/src/commands/dismiss.ts:47-55 (handler)
    The handler function runUndismiss that manages the undismiss logic by calling the state manager.
    export async function runUndismiss(options: { url: string }): Promise<UndismissOutput> {
  validateUrl(options.url);
  validateGitHubUrl(options.url, ISSUE_URL_PATTERN, 'issue');

  const stateManager = getStateManager();
  const removed = stateManager.undismissIssue(options.url);

  return { undismissed: removed, url: options.url };
}
  • packages/core/src/commands/dismiss.ts:15-18 (schema)
    Output interface for the undismiss operation.
    export interface UndismissOutput {
  undismissed: boolean;
  url: string;
}
  • packages/mcp-server/src/tools.ts:323-333 (registration)
    Tool registration for 'undismiss' within the MCP server tools configuration.
    // 19. undismiss — Undismiss an issue
server.registerTool(
  'undismiss',
  {
    description: 'Undismiss a previously dismissed issue, re-enabling notifications.',
    inputSchema: {
      url: z.string().describe('Full GitHub issue URL to undismiss'),
    },
    annotations: { readOnlyHint: false, destructiveHint: false },
  },
  wrapTool(runUndismiss),

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

Annotations indicate write operation (readOnlyHint: false) and non-destructive nature. Description adds valuable behavioral context by specifying the effect as 're-enabling notifications,' which explains what state change occurs beyond the generic 'undismiss'.

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 of 7 words. Immediately states action and effect with zero redundancy. Perfectly front-loaded and economical.

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?

Appropriately complete for a simple single-parameter state-toggle tool. Combines with annotations to explain the operation clearly, though could benefit from mentioning error behavior if called on non-dismissed issues or explicit sibling relationship to 'dismiss'.

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 description of the 'url' parameter. Description does not add explicit parameter guidance, but with complete schema coverage, the baseline score of 3 is appropriate as no additional semantic explanation is necessary.

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?

Specific verb ('Undismiss' explained as 're-enabling'), clear resource ('issue'), and clear scope ('previously dismissed') that effectively distinguishes this as the inverse of the 'dismiss' sibling tool.

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 by specifying 'previously dismissed issue,' suggesting this only works on dismissed items. However, lacks explicit 'when to use' guidance or explicit comparison to the 'dismiss' sibling tool.

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