Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get in-progress tasks and bugs for a user

get_in_progress_tasks_and_bugs

Retrieve all Tasks and Bugs currently in “In Progress” state assigned to a specific Targetprocess user ID, so you can review that user’s active workload.

Instructions

Get all Tasks and Bugs currently in "In Progress" state assigned to a given user ID

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": {
      "userId": "<userId>"
    },
    "name": "get_in_progress_tasks_and_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesTargetprocess user ID (e.g. 123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the load and does add meaningful behavior beyond the name: it discloses the state filter (only 'In Progress'), the assignment scope, and that two entity types are merged. It stops short of stating that this is a read-only operation, whether results can include items assigned via teams or roles, or how many items/which fields are returned.

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 efficient sentence, front-loaded with the verb and resources, with the two key qualifiers (state and assignee) placed where they are most useful. No filler, though the brevity leaves gaps that other dimensions penalize.

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?

This is a low-complexity, single-parameter read tool with no nested objects and no output schema, so extensive documentation is not required. Still, with no annotations and no output schema, the description should say something about the result shape (tasks vs. bugs, which fields) to be fully sufficient for an agent composing a response.

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 the single userId parameter is already documented with its meaning and an example format. The description restates that the ID is a user assignment target but adds no new semantics (e.g., whether it must be an internal Targetprocess user ID vs. an email), 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?

The description names a specific verb ('Get'), two concrete resources (Tasks and Bugs), and two filters ('currently in "In Progress" state', 'assigned to a given user ID'). An agent can tell exactly what comes back, though it does not contrast itself with similar siblings such as list_my_bugs or get_user_story_bugs.

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?

Usage is implied rather than stated: the state and assignee filters suggest 'use when you need a specific user's active work items.' There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for a broader bug listing, so the agent must infer routing from the name alone.

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