Skip to main content
Glama

OpsRev Roofing AI

Set an AccuLynx job priority

acculynx_set_job_priority
DestructiveIdempotent

Set the priority on one existing job. Confirm the job and new priority with the user before saving.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobId": "<jobId>",
      "priority": "<priority>"
    },
    "name": "acculynx_set_job_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
priorityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With annotations declaring destructiveHint=true, idempotentHint=true and readOnlyHint=false, the safety profile is already structured. The description adds a useful behavioral rule (confirm with the user before saving), but it does not state that the existing priority is overwritten or what happens on an invalid job ID, leaving gaps for a destructive mutation.

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?

Two short sentences, zero filler, with the operation stated first and the confirmation safeguard second. Every sentence carries actionable 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?

For a two-parameter destructive mutation with no output schema, the description covers the core action and one important workflow safeguard. It is still thin on what the priority values imply, what the overwrite consequences are, and what is returned after saving.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does not. It mentions the job and new priority conceptually but explains nothing about the three priority levels, their meaning, or the jobId format requirements that the schema only expresses as a regex pattern.

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 gives a specific verb and resource ('Set the priority on one existing job'), which is more precise than the title alone and clearly distinct from job creation or retrieval tools. It does not explicitly name a sibling alternative, so it stops short of a 5.

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?

The phrase 'one existing job' implies this is not for creating jobs, and the confirmation instruction gives a workflow cue. However, there is no explicit statement of when to use this instead of a general job-update tool, nor any prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources