Skip to main content
Glama

ai_modeling_jobs_list

Read-only

List and paginate persistent local jobs for the current verified account, using limit and offset controls to browse job history.

Instructions

List persistent local jobs for the current verified account.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety needs no restating. The description adds that the listing is limited to the verified account, which implies an auth requirement, but says nothing about pagination, result size caps, or whether jobs from other sources are excluded.

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?

A single front-loaded sentence with no redundant wording. Brevity is appropriate, though it comes at the cost of content rather than through efficient packing.

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

Completeness1/5

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

No output schema, no parameter explanations, and no pagination behavior are given for a list tool whose two parameters exist solely to page results. The description is too thin to tell an agent how the response behaves.

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%: both parameters (limit and offset) carry only types, defaults, and bounds, with no prose explaining their meaning. The description does not compensate at all, so an agent must infer that this listing is paginated and that limit defaults to 20.

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 persistent local jobs') plus a scope qualifier ('for the current verified account'). It is clear what the tool returns, but it never names or contrasts with the closely related ai_modeling_canvas_lab_jobs sibling, so the 'persistent local' distinction is left implicit.

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 and no alternative is named, despite a sibling that plausibly returns a different job class. The 'current verified account' scope is the only contextual hint, and it is stated as a fact rather than as a selection rule.

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