ONES Doc MCP

List ONES Requirement Bugs By Ref

list_requirement_bugs_by_ref

Read-onlyIdempotent

Retrieve bugs linked to a specific requirement using its number, task ID, or task URL. Simplify bug tracking by fetching associated issues in one call.

Instructions

List bugs under a requirement by requirement number, task id, or task URL when explicitly requested.

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": {
      "ref": "<ref>"
    },
    "name": "list_requirement_bugs_by_ref"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes

Output Schema

Name	Required	Description	Default
`bugs`	Yes
`count`	Yes
`raw_payload`	Yes
`requirement`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.1.0Oct 5, 2026
Removedv2.0.1Jul 26, 2026
First observedv1.4.0Jun 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the scoping detail that results are the bugs beneath a requirement; it says nothing about result volume, pagination, or what happens when the ref resolves to nothing.

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?

One sentence, front-loaded with the verb and resource, with no filler. It could be tightened only marginally and nothing is redundant.

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

Completeness5/5

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

With an output schema present, return-value details are unnecessary, and the annotations carry the safety profile. For a single-parameter read tool the description supplies purpose, scope, and accepted ref forms, leaving no material gap.

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 0%, so the description carries the burden for the single 'ref' parameter, and it does clarify that the value may be a requirement number, task id, or task URL. It stops short of giving the accepted formats or examples for each form, so the compensation is partial.

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 a specific verb (List) and resource (bugs under a requirement) and enumerates the three accepted reference forms (requirement number, task id, task URL). It is clearly distinguishable from get_bug_detail_by_ref and from the non-ref sibling list_requirement_bugs, though it never explicitly contrasts itself with that sibling.

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?

The phrase 'when explicitly requested' gives a weak usage condition, implying the agent should not call this proactively. However, it never states when to prefer this over list_requirement_bugs or the various get_*_by_ref siblings, so the routing guidance is only implied.

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