TDX MCP Server

tdx-kb-search

Search knowledge base articles in TeamDynamix (TDX) using text queries and filters to find solutions for IT service management issues.

Instructions

Search TDX knowledge base articles

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": "tdx-kb-search"
  }
}

Input Schema

Name	Required	Description
`appId`	No	TDX app ID (defaults to env TDX_APP_ID)
`searchText`	No	Full-text search query
`categoryIds`	No	Filter by category IDs
`status`	No	Filter by status (0=None, 1=Draft, 2=Approved, 3=Archived)
`ownerUids`	No	Filter by owner UIDs
`maxResults`	No	Max results to return (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action ('Search') without mentioning whether this is a read-only operation, if it requires authentication, what the output format looks like, or any rate limits. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. This is an excellent example of conciseness.

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

Completeness2/5

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

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the search returns (e.g., article summaries, full content, pagination), how results are ordered, or error conditions. For a search tool with rich parameters but no output schema, more context is needed.

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?

The description adds no parameter information beyond what the schema already provides. Since schema description coverage is 100%, the baseline score is 3. The description doesn't compensate with additional context like default behaviors or parameter interactions, but it also doesn't contradict the schema.

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 clearly states the tool's purpose as 'Search TDX knowledge base articles,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'tdx-kb-get' (which likely retrieves a specific article) or 'tdx-kb-create/update/delete' (which are write operations), so it falls short of a perfect score.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'tdx-kb-get' (for specific articles) or 'tdx-ticket-search' (for tickets), nor does it specify prerequisites or exclusions. This leaves the agent with minimal context for tool selection.

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