Skip to main content
Glama
Sign In
lava-mcp

lava-mcp

by mattface
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

set_job_priority

Set the queue priority of a test job to control its execution order. Provide a job ID and a priority value from 0 to 100, with higher values running sooner.

Instructions

Set a job's queue priority (0-100, higher runs sooner).

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": {
      "job_id": "<job_id>",
      "priority": "<priority>"
    },
    "name": "set_job_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
priorityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states the basic operation. It does not disclose what happens on invalid input (e.g., out-of-range priority, nonexistent job_id), whether the change is immediate or queued, or if any authentication or authorization is required.

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 concise sentence that communicates the essential purpose and constraint. No unnecessary words or details.

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 (2 required params, no output schema, no annotations), the description is minimally adequate. It misses context on error behavior, return value, and side effects, but covers the core intent.

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?

Schema coverage is 0%, so the description must add meaning. It does so for the priority parameter by specifying the range 0-100 and the order of execution. However, the job_id parameter receives no additional semantics beyond its name.

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 verb 'Set' and the resource 'job's queue priority', including the valid range and direction (higher runs sooner). It distinguishes from siblings like get_job, cancel_job, which do not modify priority.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., job state), whether to check current priority first, or any conditions under which setting priority is inappropriate.

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