Skip to main content
Glama
umzcio
by umzcio

tdx-asset-patch

Apply partial updates to TDX assets by modifying specific fields without replacing the entire record. Use this tool to change asset information in TeamDynamix while preserving existing data.

Instructions

Partial update of a TDX asset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoTDX app ID (defaults to env TDX_APP_ID)
idYesAsset ID
dataYesPartial asset data (PascalCase TDX field names)

Implementation Reference

  • Implementation of the "tdx-asset-patch" MCP tool, which performs a partial update on a TDX asset.
    server.tool(
      "tdx-asset-patch",
      "Partial update of a TDX asset",
      {
        appId: z.number().optional().describe("TDX app ID (defaults to env TDX_APP_ID)"),
        id: z.number().describe("Asset ID"),
        data: z.record(z.unknown()).describe("Partial asset data (PascalCase TDX field names)"),
      },
      async (params) => {
        const app = params.appId ?? defaultAppId;
        try {
          const result = await client.patch(`/${app}/assets/${params.id}`, params.data);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return { content: [{ type: "text", text: String(e) }], isError: true };
        }
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 of behavioral disclosure. It states 'partial update' which implies mutation, but doesn't cover permissions needed, whether changes are reversible, rate limits, or what happens to unspecified fields. This is inadequate for a mutation tool with zero annotation coverage.

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 waste. It's appropriately sized and front-loaded with the core purpose.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain behavioral traits like side effects, error conditions, or response format. Given the complexity of partial updates and lack of structured data, 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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify 'partial asset data' beyond the schema's description of 'Partial asset data (PascalCase TDX field names)'). Baseline 3 is appropriate when 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 ('partial update') and resource ('TDX asset'), which is specific and distinguishes it from generic update operations. However, it doesn't explicitly differentiate from its sibling 'tdx-asset-update', which likely performs a full update.

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?

No guidance is provided on when to use this tool versus alternatives like 'tdx-asset-update' or 'tdx-asset-create'. The description mentions 'partial update' but doesn't explain scenarios where partial updates are preferred over full updates or other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/umzcio/TeamDynamix-MCP-Connector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server