Skip to main content
Glama

get_organization_locations

Retrieve configured locations for a NinjaOne organization to manage device inventory and organization structure.

Instructions

Get the locations configured for a specific organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idYesNinjaOne organization ID

Implementation Reference

  • The handler function that executes the tool logic. It makes an API call to `/organization/${organization_id}/locations` and returns the results as JSON or an error message.
    async ({ organization_id }) => {
      try {
        const results = await client.get(
          `/organization/${organization_id}/locations`,
        );
        return toolResult(JSON.stringify(results, null, 2));
      } catch (error) {
        return toolResult(
          `Error fetching organization locations: ${error}`,
          true,
        );
      }
    },
  • Input schema definition using Zod. Requires organization_id as a number parameter with a description.
    {
      organization_id: z.number().describe("NinjaOne organization ID"),
    },
  • Complete tool registration with the MCP server. Registers the tool name, description, input schema, and handler function.
    server.tool(
      "get_organization_locations",
      "Get the locations configured for a specific organization.",
      {
        organization_id: z.number().describe("NinjaOne organization ID"),
      },
      async ({ organization_id }) => {
        try {
          const results = await client.get(
            `/organization/${organization_id}/locations`,
          );
          return toolResult(JSON.stringify(results, null, 2));
        } catch (error) {
          return toolResult(
            `Error fetching organization locations: ${error}`,
            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. It mentions retrieving locations but lacks details on permissions, rate limits, response format, or error handling. This is a significant gap for a tool with no annotation coverage.

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, clear sentence with no wasted words, making it highly concise and front-loaded. Every part of the sentence contributes directly to understanding the tool's purpose.

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 insufficient. It does not cover behavioral aspects like response format, error cases, or usage constraints, leaving gaps in understanding for effective tool invocation.

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%, with the parameter 'organization_id' fully documented in the schema. The description does not add any additional meaning or context beyond what the schema provides, so it meets the baseline of 3.

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 ('locations configured for a specific organization'), making the purpose immediately understandable. It does not explicitly differentiate from sibling tools like 'get_organization' or 'list_organizations', which prevents a score of 5.

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 'list_organizations' or 'get_organization', or any prerequisites for usage. The description only states what it does without context.

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