Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

List my bugs

list_my_bugs

Retrieve bugs assigned to you and filter by state (e.g., Open, In Progress, Fixed) to identify current issues needing attention.

Instructions

List Bugs assigned to me. Optionally filter by state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoPagination offset, default is 0
takeNoNumber of results to return, default is 25
stateNoFilter by state name (e.g. "Open", "In Progress", "Fixed")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only listing but says nothing about result ordering, pagination behavior, page size, permissions, or the shape of the response, leaving the agent to infer all operational traits.

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 short sentences with the core scope front-loaded and no filler. The second sentence is largely redundant with the state parameter's schema description, which is the only thing keeping it from a 5.

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?

For a simple read-only list tool with three optional parameters and no output schema, the description is adequate but thin. An agent still lacks any statement about pagination expectations or what a result entry contains before calling it.

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%, so skip, take, and state are already documented with defaults and examples in the schema. The description's mention of the state filter repeats the schema rather than adding syntax, matching rules, or multi-value behavior, so the baseline 3 applies.

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 and resource ('List Bugs') plus a meaningful scope qualifier ('assigned to me'), which separates it from siblings like get_release_bugs or get_user_story_bugs. It does not name any sibling explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

The only guidance is 'Optionally filter by state', which describes a parameter rather than when to choose this tool over get_in_progress_tasks_and_bugs or get_release_bugs. There are no exclusions, no prerequisites, and no stated context for using the unfiltered versus filtered form.

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

Deploy Server

Other Tools