Skip to main content
Glama

ninja_get_device_dashboard_url

Retrieve the direct URL to open a specific device in the NinjaOne web dashboard using its device ID.

Instructions

Get the direct URL to open a device in the NinjaOne web dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDevice ID

Implementation Reference

  • The handler function that executes the tool logic. It calls the NinjaOne API endpoint /device/{id}/dashboard-url to get the dashboard URL for a device.
    handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/dashboard-url`),
  • Input schema for the tool, requiring a numeric device ID.
    inputSchema: {
      type: 'object',
      required: ['id'],
      properties: {
        id: { type: 'number', description: 'Device ID' },
      },
    },
  • The tool definition is part of the deviceTools array exported from src/tools/devices.ts, which is spread into ALL_TOOLS in src/tools/index.ts.
    {
      tool: {
        name: 'ninja_get_device_dashboard_url',
        description: 'Get the direct URL to open a device in the NinjaOne web dashboard.',
        inputSchema: {
          type: 'object',
          required: ['id'],
          properties: {
            id: { type: 'number', description: 'Device ID' },
          },
        },
      },
      handler: async ({ id }, client: NinjaOneClient) => client.get(`/device/${id}/dashboard-url`),
    },
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as authentication requirements, side effects, or whether this is a read-only operation. For a simple URL retrieval, the lack of disclosure is a gap.

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 of 13 words. It is front-loaded with the action 'Get the direct URL' and is free of extraneous information.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate but does not specify the output format (e.g., a string URL). This is a minor gap in contextual completeness.

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?

The input schema has 100% description coverage for the single parameter 'id' with description 'Device ID'. The description does not add additional meaning beyond what the schema already provides.

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 retrieves a direct URL to open a device in the NinjaOne dashboard. It distinguishes itself from sibling tools that retrieve device data or perform other actions.

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?

No explicit guidance on when to use this tool versus alternatives is provided. Usage is implied by the action of obtaining a URL for a device, but no exclusions or context are given.

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