engineering-mcp

Overview Schema Source Related Servers Discussions Admin

Registrar bug

qa_record_bug

Record a local bug with severity and classification to track issues in engineering workflow. Use for immediate bug documentation, separate from corporate Jira history.

Instructions

QA: grava um bug local (severity + classificação). Para histórico Jira corporativo use o MCP qa-oracle (search_bug_history).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "qa_record_bug"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`status`	No	open, investigating, fixed, closed.
`severity`	No
`ticket_id`	No
`description`	No
`classification`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 27, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'records a local bug' without mentioning persistence, side effects, overwrite behavior, authentication, or response format. For a mutation tool this is a significant gap.

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?

Two sentences, front-loaded purpose, and an explicit alternative. No filler or redundant phrasing – every word earns its place.

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

Completeness2/5

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

With 6 parameters, no output schema, and no annotations, the description is too sparse. It does not explain what the required 'title' should be, how status values relate to the bug lifecycle, what ticket_id refers to, or what the tool returns. An agent would struggle to invoke it correctly with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% (only status has a description). The description mentions severity and classification but does not explain title, status, ticket_id, or description beyond what the schema provides. Since coverage is low, the description fails to compensate and leaves most parameters semantically underdocumented.

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?

The description states a specific verb (records) and resource (local bug) and names the key alternative (qa-oracle's search_bug_history), making it distinguishable from the corporate Jira history tool. The phrase 'severity + classification' adds clarity on the main fields involved.

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

Usage Guidelines5/5

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

Explicitly instructs when not to use this tool: 'Para histórico Jira corporativo use o MCP qa-oracle (search_bug_history).' This provides a clear when-not and names the alternative tool, which is exactly what this dimension rewards.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.