Skip to main content
Glama

aida_log_bug

Log bugs discovered during development or testing. Record bug details including title, severity level, and discovery source to track issues systematically.

Instructions

当你在开发或测试中发现 bug 时调用。记录 bug 信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesBug 描述
severityNo严重程度:critical/high/medium/low,默认 medium
sourceNo发现来源:self-review/user-feedback/testing,默认 self-review

Implementation Reference

  • The handler function 'handleLogBug' logic which registers a bug in 'run.json'.
    function handleLogBug(args: any): any {
      const severity = args.severity || 'medium';
      const source = args.source || 'self-review';
      const { path, data } = ensureRunJson();
      const id = nextId(data.bugs, 'BUG');
      const bug: BugItem = {
        bugId: id,
        title: args.title,
        severity: severity as BugItem['severity'],
        source: source as BugItem['source'],
        status: 'open',
        files: [],
        fix: null,
        taskId: data.context.currentTaskId || null,
        reportedAt: now(),
        fixedAt: null,
      };
      data.bugs.push(bug);
      data.summary.bugCount = data.bugs.length;
      addEvent(data, 'bug_created', { bugId: id });
      addTimeline(data, 'bug', `${id}: ${args.title}`);
      save(path, data);
      return { success: true, bugId: id, message: `${id} 已记录: ${args.title} [${severity}]` };
    }
  • The tool definition for 'aida_log_bug' including input schema.
      name: 'aida_log_bug',
      description: '当你在开发或测试中发现 bug 时调用。记录 bug 信息。',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Bug 描述' },
          severity: { type: 'string', enum: [...SEVERITY_VALUES], description: '严重程度:critical/high/medium/low,默认 medium' },
          source: { type: 'string', enum: [...BUG_SOURCE_VALUES], description: '发现来源:self-review/user-feedback/testing,默认 self-review' },
        },
        required: ['title'],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. Only states '记录' (records) without disclosing persistence mechanism, visibility, notifications generated, or return value. Missing behavioral traits like idempotency or confirmation.

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?

Two concise sentences, front-loaded with trigger condition. No redundant words. Could potentially combine into one sentence but structure is efficient and scannable.

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?

With no output schema and no annotations, a logging tool should ideally disclose what happens after invocation (e.g., ticket creation, notifications). Description covers minimal 'when' and 'what' but omits 'what happens next' and sibling relationships expected for a 3-param tool with side effects.

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 100% with complete Chinese documentation for each parameter. Description provides only generic '记录 bug 信息' without adding syntax guidance, validation rules, or usage tips beyond what schema already specifies. Baseline 3 appropriate.

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?

States specific trigger ('在开发或测试中发现 bug 时') and action ('记录 bug 信息'). Clear verb+resource. Loses one point because it doesn't differentiate from sibling 'aida_bug_fix' (logging vs fixing) or distinguish from other 'aida_log_*' tools.

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?

Provides implied usage context ('当...发现 bug 时调用') covering when to use. However, lacks explicit guidance on when NOT to use (e.g., vs aida_log_deviation) or workflow relationship to aida_bug_fix.

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/LWTlong/ai-dev-analytics'

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