Skip to main content
Glama
Sign In
NinjaOne MCP

NinjaOne MCP

by cyberkoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_auth_url

Generate an OAuth authorization URL for NinjaOne. Open it in a browser to log in and obtain a code to exchange for access.

Instructions

Generate a NinjaOne OAuth authorization URL. Open it in a browser to log in as yourself. After authorizing, copy the 'code' parameter from the redirect URL and pass it to exchange_code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_auth_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations present, so description carries the burden. It describes a non-destructive, read-only operation (generating URL) and mentions the OAuth flow, but does not explicitly state lack of side effects or security considerations.

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?

Three sentences, front-loaded with the core purpose, no wasted words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple 0-parameter tool, covering purpose and next step. However, it does not explicitly describe the output format (though implied it's a URL). Minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, schema coverage is 100%. The description adds context about the URL's purpose and usage, going beyond the schema.

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 clearly states the tool generates an OAuth authorization URL, using a specific verb and resource. It distinguishes from sibling tools like exchange_code by describing the next step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains the workflow: open URL in browser, authorize, copy code, pass to exchange_code. Provides clear when-to-use and sequential guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools