Skip to main content
Glama
umzcio
by umzcio

tdx-project-get

Retrieve a TeamDynamix project by its unique ID to access project details and manage IT service workflows.

Instructions

Get a TDX project by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID

Implementation Reference

  • The tool 'tdx-project-get' is registered and implemented in this block, using 'client.get' to fetch project data.
    server.tool(
      "tdx-project-get",
      "Get a TDX project by ID",
      {
        id: z.number().describe("Project ID"),
      },
      async (params) => {
        try {
          const result = await client.get(`/projects/${params.id}`);
          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 'Get' implies a read operation, but lacks details on permissions, error handling, rate limits, or response format. For a 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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like safety, permissions, or return values, which are crucial for a tool that retrieves data. The high schema coverage helps with parameters, but overall context is lacking.

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 mentions 'by ID', which aligns with the single parameter 'id' in the schema. With 100% schema description coverage, the schema already documents the parameter adequately. The description adds minimal value beyond what the schema provides, meeting the baseline for high coverage.

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 project by ID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'tdx-project-search' or 'tdx-project-update', which would require mentioning it's for retrieving a single project by its unique identifier rather than searching or modifying.

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 scenarios like needing a specific project by ID, prerequisites, or comparisons to siblings such as 'tdx-project-search' for broader queries or 'tdx-project-update' for modifications.

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