Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get card status

get_card_current_status

Retrieve the EntityState, TeamState, and assigned teams for a Targetprocess card by ID to check its current status.

Instructions

Get the EntityState, TeamState, and assigned teams for a TP card (UserStory, Bug, or Feature) by 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": {
      "id": "<id>"
    },
    "name": "get_card_current_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP card ID (e.g. 146055)
resourceTypeNoType of the TP card — UserStory, Bug, or Feature (default: UserStory)UserStory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. The verb 'Get' plus the listed return attributes make the read-only nature clear, which is useful, but there is no disclosure of error behavior for unknown IDs, permission requirements, or whether states are resolved per team versus globally.

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?

A single front-loaded sentence with the action, the resource, the identifying parameter, and the returned fields. No filler, no redundancy, and the most decision-relevant information comes first.

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

Completeness4/5

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

For a two-parameter read tool with no output schema, the description usefully names the three things it returns, which compensates for the absent output schema. It falls short only on operational details such as failure modes and access requirements, which are minor for a simple getter.

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% (the id format example and the resourceType enum with its UserStory default are already documented in the schema). The description restates 'by ID' and the card type list, adding no format, default, or constraint detail beyond the schema, 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 (Get) plus the exact resource (a TP card identified by ID) and enumerates the returned attributes: EntityState, TeamState, and assigned teams. That makes it distinguishable from siblings like get_card_relations or get_bug_content, though it does not explicitly name any sibling it should not be confused with.

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 only implied by the purpose: an agent needing the state/team assignment of a card will infer it should call this. There is no explicit when-to-use framing, no prerequisites (e.g. that the card must exist or that the caller must have access), and no named alternative for related lookups.

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