Skip to main content
Glama

decken_list_jobs

Lists recent Decken reconstruction jobs with status, slide count, and cumulative token/cost ledger to help monitor progress and costs.

Instructions

List recent Decken reconstruction jobs with status, slide count, and cumulative token/cost ledger.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the return fields (status, slide count, cumulative token/cost) and that results are bounded to "recent" jobs. It says nothing about ordering, how many jobs are returned, pagination, or whether the call has any cost or side effects beyond being a listing.

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?

A single sentence, front-loaded with the verb and resource and followed immediately by the payload contents. No filler, no restatement of the tool name, nothing that could be cut.

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, parameterless read tool with no output schema, the description covers the essential question of what the call returns, including the token/cost ledger which the agent could not otherwise guess. The remaining gap is the lack of bounds on "recent" (count, ordering, window), which matters since there is no output schema to clarify the shape.

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?

The tool takes zero parameters and the schema is an empty object with additionalProperties false, so there is no parameter meaning to add. The baseline of 4 applies for a parameterless tool with complete schema coverage.

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 opens with a specific verb and resource ("List recent Decken reconstruction jobs") and enumerates what each entry contains (status, slide count, token/cost ledger), so the agent knows exactly what comes back. It never names the nearest sibling, decken_job_status, which returns single-job status, leaving that distinction to be inferred from the word "List".

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 explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as decken_job_status for a single job. The only scoping signal is the adjective "recent", which implies it won't return full job history, but the agent gets no instruction on choosing this over the status tool.

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