Skip to main content
Glama

Background tasks, queues and crons

get_jobs
Read-only

Work done outside requests: background tasks, queue publish and process, and cron runs, with counts, failures and timings; each cron with its last run, its usual gap, and late: true when it has not run for twice that gap.

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

Input Schema

NameRequiredDescriptionDefault
toNoAn ISO time, or how long ago (default now)
fromNoAn ISO time, or how long ago: 30m, 24h, 7d
rangeNoWindow: 1h, 24h, 7d, 14d, 30d or 90d (default 24h). Ignored when from is given.
sourceNobackend (servers), frontend (app and web), or all (default)
releaseNoOnly this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185
serviceNoOnly this service, like house-ai-api or the app's bundle id
environmentNoLike production. Default: production when the app has it, else its busiest non-development one. 'all' for every environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Only this release (service version)"New value: +"Only this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real content beyond that: it discloses the returned dimensions (counts, failures, timings) and a derived field, late:true, defined precisely as twice the usual gap since last run — behavior the agent could not infer from the schema. No output schema exists, so this return-shape detail carries extra weight; pagination or result-size limits are still unstated.

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?

A single dense sentence whose main clause comes first (what the tool covers) followed by what it reports and the one non-obvious semantic detail. No filler or restatement of the title, though the semicolon clause is packed tightly enough that splitting it would improve scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, fully documented query tool with annotations but no output schema, the description covers enough: domain scope plus the key returned fields and the definition of the late flag. Remaining gaps — result volume, ordering, and whether queue and cron data are combined or separated — are minor for a read-only inspection tool.

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 description coverage is 100%, and each of the 7 parameters including the two enums is documented in the schema itself with defaults and formats. The description adds no parameter-level meaning — no hint about which filter combinations matter or how time filters interact beyond what the schema already says. Baseline 3 is appropriate.

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 names a specific domain and its three components — background tasks, queue publish/process, and cron runs — plus the shape of what is reported (counts, failures, timings). An agent can tell this is the job/queue observability tool rather than an error, trace or analytics tool. It never names a sibling to contrast against, which keeps it 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?

Usage is only implied: "Work done outside requests" suggests investigative contexts like stalled crons or failing jobs, and the late-flag detail hints at a health-check use case. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for adjacent questions such as error rates or traces.

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