Skip to main content
Glama
MCP Design System Extractor

MCP Design System Extractor

job_list

Lists all jobs with their status and shows what each job is processing and whether it is still running; optionally filter by active or completed status.

Instructions

List all jobs with their status. Shows what each job is processing and whether it is still running.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status: "all" (default), "active" (queued/running), "completed" (completed/failed/cancelled)

Output Schema

NameRequiredDescriptionDefault
jobsYes
statsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "jobs": {
      +      "items": {
      +        "properties": {
      +          "component_id": {
      +            "type": "string"
      +          },
      +          "created_at": {
      +            "type": "number"
      +          },
      +          "job_id": {
      +            "type": "string"
      +          },
      +          "started_at": {
      +            "type": "number"
      +          },
      +          "status": {
      +            "enum": [
      +              "queued",
      +              "running",
      +              "completed",
      +              "failed",
      +              "cancelled"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "job_id",
      +          "status",
      +          "component_id",
      +          "created_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "stats": {
      +      "properties": {
      +        "completed": {
      +          "type": "number"
      +        },
      +        "failed": {
      +          "description": "Includes cancelled jobs",
      +          "type": "number"
      +        },
      +        "queued": {
      +          "type": "number"
      +        },
      +        "running": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "queued",
      +        "running",
      +        "completed",
      +        "failed"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "jobs",
      +    "stats"
      +  ],
      +  "type": "object"
      +}
  2. Addedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden, and it does signal a read-only enumeration that reports processing state and running status. It says nothing about result volume, ordering, pagination, or whether large job sets are truncated — gaps that matter for a list tool with no annotations.

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?

Two short sentences, front-loaded with the operation. The second sentence partly restates the first ("with their status" vs "whether it is still running"), but it adds the processing-detail payoff, so it still earns its place.

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 one-parameter, zero-required read tool with a full output schema and complete schema descriptions, this is close to sufficient. The only shortfall is the absence of any routing note toward the sibling job_status/job_cancel tools.

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 100% and the status enum is fully documented in the schema, including the mapping of "active" to queued/running and "completed" to completed/failed/cancelled. The description adds no filter semantics of its own and in fact could mislead slightly by saying "all jobs" while a status filter exists.

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 ("List all jobs") plus what the result conveys ("their status", "what each job is processing"). It is distinguishable from job_status/job_cancel by the plural scope, though the description never names those siblings to make the contrast explicit.

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?

There is no when-to-use or when-not-to-use guidance. With three related siblings (job_status, job_cancel) present, an agent gets no instruction on when enumeration is preferable to a single-job lookup; the only hint is the implicit "all jobs" plural scope.

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