Skip to main content
Glama

ninja_get_organization

Retrieve detailed information about a specific organization by its ID. Access organization-specific data for management and reporting.

Instructions

Get detailed information about a specific organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrganization ID

Implementation Reference

  • Tool definition and handler for 'ninja_get_organization'. Makes a GET request to /organization/{id} to retrieve detailed info about a specific organization. Requires 'id' parameter.
    {
      tool: {
        name: 'ninja_get_organization',
        description: 'Get detailed information about a specific organization.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Organization ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) => client.get(`/organization/${id}`),
    },
  • Input schema for 'ninja_get_organization'. Requires an object with a required numeric 'id' property describing the organization ID.
    tool: {
      name: 'ninja_get_organization',
      description: 'Get detailed information about a specific organization.',
      inputSchema: {
        type: 'object',
        required: ['id'],
        properties: {
          id: { type: 'number', description: 'Organization ID' },
        },
      },
  • src/tools/index.ts:5-5 (registration)
    Import of organizationTools from the organizations module, which includes the 'ninja_get_organization' tool definition.
    import { organizationTools } from './organizations.js';
  • ALL_TOOLS array where organizationTools (including 'ninja_get_organization') are spread and exported for registration.
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • ToolDef interface defining the shape of tool objects: a 'tool' (name, description, inputSchema) and a '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 exist, and the description does not disclose any behavioral traits, such as read-only nature, authentication requirements, or error handling. The burden is on the description, but it only states it 'gets' information, which is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at one sentence. However, it could be more informative without increasing verbosity. It earns a high score for efficiency but loses points for not including crucial details.

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 output schema and the presence of many sibling tools that retrieve organization-related data, the description is incomplete. It does not specify what 'detailed information' includes, leaving the agent uncertain about the return value.

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 input schema fully describes the single parameter 'id' with a simple description. The tool description does not add any additional semantic meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 verb 'get' and the resource 'detailed information about a specific organization'. However, it does not distinguish from sibling tools like 'ninja_get_organizations_detailed', which also provides detailed organization data.

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, such as 'ninja_get_organization_custom_fields' or 'ninja_get_organization_devices'. The description lacks context for selection.

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