Skip to main content
Glama
Sign In
kt-mcp

kt-mcp

by DNLINYJ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

job_status

Read-only

Retrieve a retained job by ID or list available jobs; results are bounded in memory and lost on restart.

Instructions

Get a retained job or list jobs. Results are bounded in memory and lost on restart.

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

Input Schema

NameRequiredDescriptionDefault
job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are memory-bounded and lost on restart, warning the agent about retention limits. It omits pagination/result-size handling for the list mode.

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, purpose front-loaded, with the volatile-retention caveat immediately after. Nothing redundant.

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

Completeness3/5

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

There is no output schema, so the description should describe what a job record contains (state, exit code, timings) — it does not. 'Retained' is also left undefined, so the agent cannot tell which jobs remain queryable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden, and it does explain the key semantic: supplying job_id retrieves one job, omitting it lists jobs. It adds no detail on job_id format or origin (where IDs come from), which is a minor gap.

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 states a specific verb and resource: 'Get a retained job or list jobs.' It also conveys the dual mode (single-retrieve vs enumerate) driven by the optional job_id. It does not name job_wait or job_cancel to differentiate, though their names make the boundary fairly obvious.

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 implied by 'retained job' — only jobs still held in memory are addressable — but the description never states when to call this versus job_wait (blocking) or job_cancel. The agent must infer the alternatives from sibling names alone.

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