Skip to main content
Glama

ninja_update_organization

Update an existing organization's name, description, or device approval mode by providing its ID.

Instructions

Update an existing organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOrganization ID
nameNoOrganization name
descriptionNoOrganization description
nodeApprovalModeNoHow new devices are approved

Implementation Reference

  • The handler function for ninja_update_organization. It destructures 'id' from args and passes the rest as body to a PATCH request to /organization/{id}.
      handler: async ({ id, ...body }, client: NinjaOneClient) =>
        client.patch(`/organization/${id}`, body),
    },
Behavior2/5

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

No annotations provided; description only says 'update' without disclosing side effects, idempotency, permissions, or behavior for omitted fields. For a mutation tool, this 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.

Conciseness5/5

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

Single sentence, no wasted words. Efficiently conveys the core purpose despite minimal detail.

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?

Missing return value description (no output schema). No context on behavior like partial updates, error conditions, or required permissions. Incomplete for a mutation tool.

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?

Input schema covers all 4 parameters with descriptions (100% coverage). The tool description adds no additional meaning beyond the schema, earning baseline score.

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 it updates an existing organization, distinguishing it from related tools like ninja_create_organization and ninja_get_organization. However, it does not enumerate updatable fields, which are only in the schema.

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 (e.g., create vs update). No mention of prerequisites or scenarios where update is appropriate.

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