Skip to main content
Glama

status

Read-only

Check current pull request tracking status to monitor open PRs, shelved PRs, and dismissed issues for open source project management.

Instructions

Show current PR tracking status including open PRs, shelved PRs, and dismissed issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offlineNoIf true, show only locally cached state without fetching from GitHub

Implementation Reference

  • The handler function for the "status" tool, which reads contribution statistics from the local state.
    export async function runStatus(options: StatusOptions): Promise<StatusOutput> {
      const stateManager = getStateManager();
      const stats = stateManager.getStats();
      const state = stateManager.getState();
    
      // Status always reads from local state (no API calls), so offline mode
      // simply adds metadata about cache freshness.
      const lastUpdated = state.lastDigestAt || state.lastRunAt;
    
      // Extract only the stats we want to output (exclude totalTracked)
      const { totalTracked: _totalTracked, ...outputStats } = stats as typeof stats & { totalTracked?: number };
      const output: StatusOutput = {
        stats: outputStats,
        lastRunAt: state.lastRunAt,
      };
      if (options.offline) {
        output.offline = true;
        output.lastUpdated = lastUpdated;
      }
    
      return output;
    }
  • Registration of the "status" tool in the MCP server.
    // 2. status — Show tracking status
    server.registerTool(
      'status',
      {
        description: 'Show current PR tracking status including open PRs, shelved PRs, and dismissed issues.',
        inputSchema: {
          offline: z
            .boolean()
            .optional()
            .describe('If true, show only locally cached state without fetching from GitHub'),
        },
        annotations: { readOnlyHint: true },
      },
      wrapTool(runStatus),
    );
Behavior3/5

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

Annotations establish readOnlyHint=true; description adds value by disclosing what data categories are returned (open/shelved/dismissed). Does not elaborate on caching behavior, rate limits, or output format beyond listing categories.

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, efficient sentence with zero waste. Information is front-loaded with action verb followed immediately by resource and scope details.

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?

Appropriate for low-complexity tool (1 optional param, read-only). Description compensates for missing output schema by enumerating three data categories returned. Minor gap: does not describe output formatting or when to prefer offline mode.

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% for the single 'offline' parameter, establishing baseline 3. Description does not mention the parameter, but given high schema coverage, no additional penalty applied.

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 provides specific verb ('Show'), clear resource ('PR tracking status'), and enumerates scope ('open PRs, shelved PRs, and dismissed issues'). Effectively distinguishes from action-oriented siblings like track, shelve, dismiss, claim, and move.

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?

Clearly implies read-only inspection use case through 'Show' verb and content listing, but lacks explicit 'when to use' guidance (e.g., 'Use this before modifying PRs') or comparison to siblings like check-setup or daily. Offline parameter usage is left to schema documentation.

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