Skip to main content
Glama
Sign In
@ainize/mcp

@ainize/mcp

Official
by ainblockchain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List jobs

job_list
Read-only

Lists jobs started in this MCP session, newest first, enabling agents to recover lost job IDs; finished jobs are evicted after 30 minutes.

Instructions

The jobs this MCP session started, newest first — so a conversation that lost a job_id is not stuck. Jobs are evicted 30 minutes after they finish.

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
kindNo
limitNo
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile. The description adds genuinely useful behavior beyond that: session-scoped results, newest-first ordering, and 30-minute post-completion eviction — the last item materially affects whether a lookup will succeed. It stops short of saying what a returned job record contains.

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 compact sentences with the scope stated first and the retention caveat second. Every clause adds information an agent needs; nothing is padded.

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 read-only list with three optional filters and no output schema, the description supplies the two things most likely to cause a wrong call: session scoping and the 30-minute eviction window. The unfiltered/unexplained filter parameters are the remaining gap.

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 description coverage is 0%, so the description must carry parameter meaning, and it carries none — the kind, state, and limit filters are never mentioned or explained. The only related detail is job_id, which is not a parameter of this tool.

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 implied (list) and resource (jobs), plus a crucial scope: only jobs this MCP session started, ordered newest first. That scope implicitly separates it from job_status (single job by id) and job_cancel, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger for use: recovering when a conversation has lost a job_id. Clear context, but no explicit when-not or pointer to job_status for the case where the id is known.

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