Skip to main content
Glama

ninja_get_integrity_check_jobs

Retrieve backup integrity check job results with device filtering and pagination support.

Instructions

Get backup integrity check job results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoDevice filter expression
pageSizeNoMax results to return
cursorNoPagination cursor from previous response

Implementation Reference

  • The handler function for ninja_get_integrity_check_jobs. It makes a GET request to '/backup/integrity-check-jobs' with cleaned query parameters via the NinjaOneClient.
    handler: async (args, client: NinjaOneClient) =>
      client.get('/backup/integrity-check-jobs', clean(args)),
  • The tool definition including name ('ninja_get_integrity_check_jobs'), description, and inputSchema (df, pageSize, cursor).
    tool: {
      name: 'ninja_get_integrity_check_jobs',
      description: 'Get backup integrity check job results.',
      inputSchema: {
        type: 'object',
        properties: {
          df: { type: 'string', description: 'Device filter expression' },
          pageSize: { type: 'number', description: 'Max results to return' },
          cursor: { type: 'string', description: 'Pagination cursor from previous response' },
        },
      },
  • The backupTools array (containing this tool's definition) is exported from 'backup.ts' and spread into ALL_TOOLS, which is used by the MCP server to register tools.
    import { backupTools } from './backup.js';
    import { deviceTools } from './devices.js';
    import { organizationTools } from './organizations.js';
    import { policyTools } from './policies.js';
    import { queryTools } from './queries.js';
    import { systemTools } from './system.js';
    import { ticketingTools } from './ticketing.js';
    import { userTools } from './users.js';
    export type { ToolDef } from './types.js';
    
    export const ALL_TOOLS = [
      ...deviceTools,
      ...organizationTools,
      ...alertTools,
      ...activityTools,
      ...ticketingTools,
      ...queryTools,
      ...policyTools,
      ...userTools,
      ...backupTools,
  • The 'clean' utility removes null/empty values from args before passing them as query parameters to the API call.
    export function clean(args: Record<string, any>): Record<string, unknown> {
      return Object.fromEntries(
        Object.entries(args).filter(([, v]) => v != null && v !== ''),
      );
  • src/index.ts:24-24 (registration)
    The main server entry point builds a toolMap from ALL_TOOLS, mapping tool name to handler, and dispatches incoming CallToolRequest calls to the appropriate handler.
    const toolMap = new Map(ALL_TOOLS.map((def) => [def.tool.name, def.handler]));
Behavior2/5

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

No annotations exist, so the description must fully convey behavioral traits. It does not mention side effects, permissions required, rate limits, or whether the operation is read-only (likely, but unstated). The minimal description leaves significant behavioral uncertainty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, concise sentence with no extraneous words. However, it lacks any structure (e.g., paragraphs or bullet points) that could improve readability for complex tools. For a simple tool, this is acceptable but not exemplary.

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 absence of an output schema and annotations, the description should provide more context about the return format, pagination via cursor, filtering via df, and the nature of the results. It fails to do so, leaving the agent with insufficient information to use the tool effectively.

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 schema covers all three parameters with descriptions (100% coverage). The tool description adds no additional meaning or context to the parameters, so it scores at the baseline for high schema coverage.

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 'Get backup integrity check job results' clearly states the action (get) and resource (backup integrity check job results). However, it does not differentiate itself from the sibling tool 'ninja_get_backup_jobs', which might serve a similar purpose for regular backup jobs. The purpose is clear but lacks sibling distinction.

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 guidelines are provided on when to use this tool versus alternatives like 'ninja_get_backup_jobs'. There is no context on appropriate scenarios, prerequisites, or conditions that would favor this tool over others.

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