Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Search TP cards by keyword or phrase in description

search_tp_cards

Search Targetprocess cards (User Stories or Bugs) by keyword or partial phrase in descriptions, with fallback searches by individual words or Generals entities when no matches are found.

Instructions

Searches TP cards (UserStories or Bugs) by keyword or phrase or partial keyphrase in Card Description e.g. "Text Element", "Font field" NOTE: after results are returned, try analyze and filter results by most relevant to what user is looking for in the description text FALLBACK: if no results are found, try spliting phrase by spaces and searching for each word and with "Generals" entity type

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": {
      "keyword": "<keyword>"
    },
    "name": "search_tp_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword or partial name or keyphrase to search for in description
entityTypeNoType of TP entity to search — UserStories or Bugs (default: UserStories)UserStories

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?

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the search surface (Card Description only) and the default entity type, but says nothing about result limits, pagination, case sensitivity, substring vs full-text matching, or permissions, which matter for a search tool whose results the agent is told to re-rank.

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?

Front-loaded with the core purpose, then cleanly split into NOTE and FALLBACK blocks so each piece of guidance is easy to locate. Minor waste and roughness remain—the embedded examples are redundant with the schema's keyword description, and "spliting" plus inconsistent quoting slightly reduce polish.

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 and no annotations, the description covers the essentials: what is searched, what is returned conceptually, how to post-process results, and what to do on empty results. Only the shape and volume of returned results remain unaddressed, which is a modest gap given no output schema exists to explain 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 description coverage is 100%, so both parameters are already documented, and this sets the baseline at 3. The description adds only marginal meaning: it implies the keyword is matched against description text and reveals via the fallback that "Generals" is a usable entityType value, though the purpose sentence mentions only UserStories or Bugs, leaving the enum's third value explained only indirectly.

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 (searches TP cards) and narrows the scope to matches in Card Description, with concrete examples ("Text Element", "Font field"). It clarifies the entity types covered, but never names a sibling tool as the alternative, so an agent must infer how it differs from tools like get_release_user_stories_with_description.

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

Usage Guidelines4/5

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

Goes beyond a bare description by giving a post-search workflow (analyze and rank results by relevance) and an explicit fallback strategy (split the phrase into individual words, retry with the "Generals" entity type). It lacks any when-not-to-use condition or pointer to a sibling for non-description searches, which keeps it below a 5.

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