Skip to main content
Glama

get_organization

Retrieve organization details including contact information, assigned tags, and policy configurations using the NinjaOne organization ID.

Instructions

Get detailed information about a specific organization by its ID, including contact info, tags, and policy assignments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesNinjaOne organization ID

Implementation Reference

  • Handler for 'get_organization' tool. Makes API call to /organization/{id} endpoint and returns JSON result or error.
    server.tool(
      "get_organization",
      "Get detailed information about a specific organization by its ID, including contact info, tags, and policy assignments.",
      {
        organization_id: z.number().describe("NinjaOne organization ID"),
      },
      async ({ organization_id }) => {
        try {
          const result = await client.get(`/organization/${organization_id}`);
          return toolResult(JSON.stringify(result, null, 2));
        } catch (error) {
          return toolResult(
            `Error fetching organization: ${error}`,
            true,
          );
        }
      },
    );
  • Zod schema defining the input parameter for get_organization tool - organization_id as a required number.
    {
      organization_id: z.number().describe("NinjaOne organization ID"),
    },
  • src/index.ts:37-37 (registration)
    Registration of organization tools including get_organization in the main server setup.
    registerOrganizationTools(server, client);
  • Helper function to format tool responses in MCP format with content array and optional error flag.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
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. It mentions what information is returned but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or whether this is a read-only operation. The description is functional but lacks operational context.

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, well-structured sentence that efficiently communicates the tool's purpose and scope. Every word earns its place with no redundancy or unnecessary elaboration.

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?

For a simple read operation with one parameter and no output schema, the description is adequate but minimal. It covers the basic purpose and return data types, but lacks context about authentication, error handling, or relationship to sibling tools that would help an agent use it correctly.

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 the 'organization_id' parameter. The description adds marginal value by specifying it's a 'NinjaOne organization ID' and that it retrieves 'detailed information', but doesn't provide additional semantics beyond what the schema offers.

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 resource 'organization' with specific details like 'contact info, tags, and policy assignments'. It distinguishes from siblings like 'list_organizations' by focusing on a single organization by ID, though it doesn't explicitly name alternatives.

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?

The description implies usage when detailed information about a specific organization is needed, but doesn't explicitly state when to use this vs alternatives like 'list_organizations' or 'get_organization_locations'. No exclusions or prerequisites are mentioned.

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/fredriksknese/mcp-ninjaone'

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