forge3d-mcp

List Jobs

list_jobs

Lists recent 3D generation jobs, newest first, with an optional limit to control how many results are returned.

Instructions

Recent generation jobs, newest first.

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

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.7Nov 4, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It discloses ordering but not whether jobs are filtered by status, whether failed jobs appear, how far back "recent" reaches, or what happens when the result set exceeds the limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The phrase is front-loaded and free of filler, but it is undersized rather than concise for a tool with an undocumented parameter and no annotations. A few more words on scope would cost little and add a lot.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but with zero annotation coverage and 0% parameter documentation the definition leaves the agent without the essentials: result bounds, recency window, and filtering behavior.

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% and the single parameter (limit, default 20) is never mentioned in the description. Neither the cap on results nor the ability to raise/lower it is explained anywhere, so the agent learns nothing about the only knob available.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Recent generation jobs, newest first" identifies the resource (generation jobs) and the sort order, but uses no verb and never distinguishes itself from the closely-named sibling get_job, which presumably returns a single job. The ordering detail is the only thing added beyond the tool name.

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 statement of when to call this versus get_job, no mention of how "recent" is bounded, and no note about pagination or how to retrieve older jobs. The agent is left to infer the entire selection context from the name alone.

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