Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read Service Job Details

readServiceJobDetails
Read-only

Inspect service job runs to see states, attempts, runtimes, and errors, plus scheduled jobs, recent failures by job type, and failed or dead queue jobs for debugging.

Instructions

Returns the newest job runs with their state, attempt, run time and error text, the jobs that schedules added within the range, the newest failure of each job type, and up to three failed or dead jobs per queue. Requires the developer role, because error texts can carry job data.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>",
      "serviceName": "<serviceName>"
    },
    "name": "readServiceJobDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
rangeNoHow far back to look; the answer has 30 to 96 points across it1h
regionNo
appSlugYes
serviceNameYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior; the description adds the developer-role requirement and the reason (error texts can carry job data), plus concrete return scope and per-queue limits. It does not cover pagination or how 'newest' is bounded, but the added behavioral context is substantial.

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 compact and front-loads the returned data before the permission note. The first sentence is a dense multi-clause list that could be easier to scan, but no sentence is wasted.

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?

No output schema exists, so the description has to carry the return-value burden; it does so with a detailed inventory of job-run, schedule, failure, and per-queue data. It remains incomplete on parameter meanings and sibling choice, but for a read-only diagnostic tool the core behavioral picture is present.

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 coverage is only 17%, with just the range enum described; the description clarifies that range also governs schedule-added jobs but says nothing about env, region, workspaceSlug, appSlug, or serviceName. With five of six parameters undocumented in the schema, this leaves meaningful gaps.

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?

States a specific verb and resource: returns newest job runs with state, attempt, run time, error text, schedule-added jobs, newest failures, and up to three failed/dead jobs per queue. The scope is clear enough to distinguish it from a simple job list, but it never names the sibling readServiceJobs or explicitly contrasts the two.

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?

The only usage-adjacent statement is the developer-role prerequisite, which is a permission requirement rather than a when-to-use rule. It gives no guidance on choosing this over readServiceJobs or retryServiceJobs, and no exclusions.

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