Skip to main content
Glama

ninja_get_ticket_attributes

Retrieve custom attribute definitions for tickets to manage and utilize custom fields in your NinjaOne RMM platform.

Instructions

Get the custom attribute definitions available for tickets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition for 'ninja_get_ticket_attributes' with its handler that calls GET /ticketing/attributes to retrieve custom attribute definitions for tickets.
      tool: {
        name: 'ninja_get_ticket_attributes',
        description: 'Get the custom attribute definitions available for tickets.',
        inputSchema: { type: 'object', properties: {} },
      },
      handler: async (_args, client: NinjaOneClient) => client.get('/ticketing/attributes'),
    },
  • Input schema for 'ninja_get_ticket_attributes' — an empty object (no parameters required).
    inputSchema: { type: 'object', properties: {} },
  • The tool is registered via the ticketingTools array, which is spread into ALL_TOOLS and then mapped into the MCP server's tool list and handler map in src/index.ts (lines 24 and 32).
    export const ALL_TOOLS = [
  • The ToolDef type that defines the shape of each tool definition, including the tool metadata and handler function.
    export interface ToolDef {
      tool: Tool;
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      handler: (args: any, client: NinjaOneClient) => Promise<unknown>;
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Get' (read) but omits details like permissions needed, whether definitions are metadata vs values, or any limitations. More transparency on what 'definitions' entails would help.

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?

Single, front-loaded sentence with zero waste. Efficiently conveys purpose.

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?

Adequate for a zero-parameter tool, but lacks explanation of 'definitions' (e.g., if they include names, types, options). Given sibling richness, a slightly more detailed description could improve completeness.

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 has no parameters, so schema description coverage is 100%. Baseline 3 applies; description adds no parameter info beyond schema since none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Description clearly states the tool retrieves 'custom attribute definitions available for tickets'. Verb 'Get' and resource 'custom attribute definitions' are specific, and the scope 'for tickets' distinguishes it from siblings like ninja_get_device_custom_fields (device-specific) and ninja_list_custom_fields (generic).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for fetching ticket custom attribute definitions, but no explicit when-to-use/alternatives guidance. Siblings for other entities exist but are not mentioned, leaving the agent to infer applicability.

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/Allied-Business-Solutions/ninjaone-mcp'

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