TDX MCP Server

tdx-people-update

Update TDX person records by providing UID and field data to modify employee information in the system.

Instructions

Update a TDX person

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>",
      "data": "<data>"
    },
    "name": "tdx-people-update"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	Person UID
`data`	Yes	Person data (PascalCase TDX field names)

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 states 'Update' which implies a mutation, but doesn't mention required permissions, whether changes are reversible, potential side effects (e.g., on related records), or error conditions. For a mutation 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 immediately scannable. Every word earns its place by conveying essential information without redundancy.

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 this is a mutation tool with no annotations, no output schema, and complex nested parameters ('data' is an object with additionalProperties), the description is incomplete. It doesn't address behavioral aspects like authentication needs, rate limits, or what the tool returns upon success/failure. The agent lacks crucial context for safe and effective 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?

Schema description coverage is 100%, so the schema already documents both parameters ('uid' and 'data') with basic descriptions. The description adds no additional meaning about parameter usage, such as format examples for 'data' or how 'uid' relates to other tools. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Update') and resource ('a TDX person'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'tdx-people-search' or other update tools like 'tdx-asset-update' or 'tdx-ticket-update', which would require more specificity about what constitutes a 'person' versus other entity types.

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 prerequisites (e.g., needing a person UID from 'tdx-people-get' or 'tdx-people-search'), nor does it clarify use cases like modifying person attributes versus creating new records with 'tdx-account-get' tools. This leaves the agent guessing about appropriate contexts.

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