Skip to main content
Glama
Sign In
contextium-mcp-server

contextium-mcp-server

Official
by contextium-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

list_agent_jobs

List recent agent runner jobs for a workspace, showing status, intent, and result summary to monitor workflow execution.

Instructions

List recent agent runner jobs for the workspace — shows status (pending, running, done, failed), intent, and result summary.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace ID. Defaults to your active workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions listing recent jobs with status, intent, result summary, but does not disclose ordering, pagination, limits, or authorization requirements. Adequate for a simple read tool.

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?

Single sentence with no wasted words. All key information is front-loaded: action, resource, and displayed fields.

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 simple tool with one optional parameter and no output schema, the description adequately covers what the tool does and what it returns. Lacks only minor details like default ordering or limit.

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% for the single optional parameter 'workspaceId'. The description adds no additional meaning beyond the schema. Baseline score of 3 applies.

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 action (list) and resource (recent agent runner jobs), and specifies what information is shown (status, intent, result summary). It is distinct from sibling tools like list_agents and get_agent_job.

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 explicit guidance on when to use this tool versus alternatives like get_agent_job. The description implies it's for listing recent jobs but lacks when-not-to-use or alternative suggestions.

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