Skip to main content
Glama

ninja_create_organization_location

Create a location for an organization by specifying ID, name, address, city, state, country, and postal code.

Instructions

Create a new location for an organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrganization ID
nameYesLocation name
descriptionNoLocation description
addressNoStreet address
cityNoCity
stateNoState or province
countryNoCountry code (e.g. US)
zipCodeNoPostal/ZIP code

Implementation Reference

  • Handler function for ninja_create_organization_location - makes a POST request to /organization/{id}/locations with the request body (name, description, address, etc.)
    handler: async ({ id, ...body }, client: NinjaOneClient) =>
      client.post(`/organization/${id}/locations`, body),
  • Input schema for ninja_create_organization_location - requires 'id' (number) and 'name' (string), with optional fields: description, address, city, state, country, zipCode
    inputSchema: {
      type: 'object',
      required: ['id', 'name'],
      properties: {
        id: { type: 'number', description: 'Organization ID' },
        name: { type: 'string', description: 'Location name' },
        description: { type: 'string', description: 'Location description' },
        address: { type: 'string', description: 'Street address' },
        city: { type: 'string', description: 'City' },
        state: { type: 'string', description: 'State or province' },
        country: { type: 'string', description: 'Country code (e.g. US)' },
        zipCode: { type: 'string', description: 'Postal/ZIP code' },
      },
    },
  • Tool registration as part of organizationTools array - the tool object with name: 'ninja_create_organization_location' and its handler
    {
      tool: {
        name: 'ninja_create_organization_location',
        description: 'Create a new location for an organization.',
        inputSchema: {
          type: 'object',
          required: ['id', 'name'],
          properties: {
            id: { type: 'number', description: 'Organization ID' },
            name: { type: 'string', description: 'Location name' },
            description: { type: 'string', description: 'Location description' },
            address: { type: 'string', description: 'Street address' },
            city: { type: 'string', description: 'City' },
            state: { type: 'string', description: 'State or province' },
            country: { type: 'string', description: 'Country code (e.g. US)' },
            zipCode: { type: 'string', description: 'Postal/ZIP code' },
          },
        },
      },
      handler: async ({ id, ...body }, client: NinjaOneClient) =>
        client.post(`/organization/${id}/locations`, body),
  • ALL_TOOLS array that exports organizationTools (which contains the tool) to the main server registration
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
      ...systemTools,
    ];
  • src/index.ts:24-24 (registration)
    Main server registration - toolMap built from ALL_TOOLS, mapping tool name to handler, used in CallToolRequestSchema handler
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
Behavior1/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'Create', which implies a mutation, but omits any side effects, authorization needs, or error handling (e.g., what happens if organization ID is invalid).

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, concise sentence that gets straight to the point with no unnecessary words.

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 complexity of a creation tool with 8 parameters and no output schema, the description is incomplete. It does not specify the return value (e.g., created location ID) or any post-creation behavior, leaving the agent without crucial information.

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?

All 8 parameters have descriptions in the input schema (100% coverage), so the description adds no additional meaning beyond what the schema already provides, earning a baseline score of 3.

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?

The description specifies the action 'Create' and the resource 'a new location for an organization', which clearly distinguishes it from sibling tools like 'create_organization' or 'list_locations'.

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 on when to use this tool versus alternatives, nor any prerequisites (e.g., organization must exist). The description is purely declarative.

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