TDX MCP Server

tdx-people-get

Retrieve a person's information from TeamDynamix using their unique identifier (UID) to access contact details and user data.

Instructions

Get a TDX person by UID

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": {
      "uid": "<uid>"
    },
    "name": "tdx-people-get"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	Person UID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 18, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a read operation ('Get'), implying non-destructive behavior, but doesn't disclose any behavioral traits such as authentication requirements, rate limits, error handling (e.g., what happens if the UID is invalid), or response format. This leaves significant gaps for an agent to understand how to use it effectively.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes essential information.

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?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage guidelines. Without annotations or output schema, the agent must infer behavior from the description alone, which is insufficient for fully informed use.

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 input schema has 100% description coverage, with the 'uid' parameter documented as 'Person UID'. The description adds no additional semantic context beyond this, such as UID format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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 action ('Get') and resource ('a TDX person'), and specifies the lookup method ('by UID'). It distinguishes from sibling tools like 'tdx-people-search' and 'tdx-people-lookup' by focusing on direct UID-based retrieval. However, it doesn't explicitly contrast with 'tdx-account-get' which might retrieve similar data through a different identifier.

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 like 'tdx-people-search' (for broader queries) or 'tdx-people-lookup' (for other lookup methods). It lacks context about prerequisites (e.g., needing a valid UID) or exclusions (e.g., not for creating or updating people).

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