Skip to main content
Glama

job_count

Counts jobs matching filter criteria so you can assess backlog size before listing. Use it to gauge job volume and plan queries.

Instructions

Count jobs matching filter criteria. Use to assess backlog size before listing.

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": "job_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNo
activeNo
jobIdsNo
timersNo
acquiredNo
dueDatesNo
messagesNo
suspendedNo
activityIdNo
executableNo
tenantIdInNo
createTimesNo
executionIdNo
noRetriesLeftNo
withExceptionNo
jobDefinitionIdNo
withRetriesLeftNo
withoutTenantIdNo
exceptionMessageNo
failedActivityIdNo
processInstanceIdNo
processInstanceIdsNo
processDefinitionIdNo
processDefinitionKeyNo
priorityLowerThanOrEqualsNo
includeJobsWithoutTenantIdNo
priorityHigherThanOrEqualsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv1.3.0
    • addedInput schema / properties / acquired
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / activityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createTimes
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueDates
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / exceptionMessage
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executable
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / failedActivityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / includeJobsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / jobDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobIds
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / messages
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / noRetriesLeft
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / priorityHigherThanOrEquals
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / priorityLowerThanOrEquals
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceIds
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / suspended
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / timers
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withException
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withRetriesLeft
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only counting operation but says nothing about what is returned (a bare number vs. an object), whether counting over large job sets is expensive, or any permission requirements — significant gaps for a 27-parameter tool with zero annotation coverage.

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 with zero filler, and the core action is front-loaded ahead of the usage hint. Nothing can be trimmed without losing information.

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 27 undocumented parameters, no annotations, and no output schema, the definition is too thin. An agent still lacks filter semantics, combination behavior, and the shape of the returned count, so it is not complete enough for reliable invocation.

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 27 filter parameters must be explained by the description, which adds only the generic phrase 'matching filter criteria'. It does not clarify date-range formats, range parameters like priorityLowerThanOrEquals, or how the boolean flags combine, leaving the agent to infer everything from parameter names.

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 ('Count jobs') plus scope ('matching filter criteria'), so an agent can tell this apart from list-style tools. It stops short of naming job_list explicitly, relying on the phrase 'before listing' to imply the 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 Guidelines4/5

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

It states a clear usage context ('Use to assess backlog size before listing'), which effectively routes the agent toward counting before listing. It gives no explicit when-not conditions or prerequisites, so it falls short of a 5.

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