Skip to main content
Glama
umzcio
by umzcio

tdx-cmdb-delete

Remove configuration items from the TDX CMDB by specifying the CI ID to manage IT asset records.

Instructions

Delete a TDX configuration item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoTDX app ID (defaults to env TDX_APP_ID)
idYesCI ID

Implementation Reference

  • The tool 'tdx-cmdb-delete' is registered and implemented in src/tools/cmdb.ts. The handler uses the 'tdx-client' instance to perform a DELETE request to the TDX API.
    server.tool(
      "tdx-cmdb-delete",
      "Delete a TDX configuration item",
      {
        appId: z.number().optional().describe("TDX app ID (defaults to env TDX_APP_ID)"),
        id: z.number().describe("CI ID"),
      },
      async (params) => {
        const app = params.appId ?? defaultAppId;
        try {
          await client.delete(`/${app}/cmdb/${params.id}`);
          return { content: [{ type: "text", text: "CI deleted successfully" }] };
        } 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 full burden. While 'Delete' clearly indicates a destructive operation, the description provides no additional behavioral context: no information about permissions required, whether deletion is reversible, what happens to related data, confirmation requirements, or rate limits. For a destructive operation with zero annotation coverage, this is a significant gap.

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 appropriately sized for a simple deletion operation and front-loads the essential information. Every word earns its place.

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 destructive operation with no annotations and no output schema, the description is inadequate. It doesn't explain what a 'configuration item' is (versus assets, KB articles, etc.), doesn't warn about irreversible consequences, doesn't mention authentication or permission requirements, and provides no information about response format or error conditions. Given the tool's destructive nature and lack of structured metadata, 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 both parameters (appId defaults to environment variable, id is required CI ID). The description adds no parameter information beyond what's in the schema - it doesn't explain what a 'CI ID' represents, format expectations, or validation rules. 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Delete') and resource ('TDX configuration item'), which provides basic purpose. However, it doesn't differentiate this from sibling tools like 'tdx-asset-delete' or 'tdx-kb-delete' - all are deletion operations on different resource types. The description is vague about what specifically distinguishes a 'configuration item' from other deletable entities.

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 about when to use this tool versus alternatives. With multiple deletion tools available (tdx-asset-delete, tdx-kb-delete, tdx-cmdb-delete), the description offers no context about which resource type this applies to, nor any prerequisites or warnings about using a destructive operation. The agent must infer usage from the tool name alone.

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