Skip to main content
Glama

decken_job_status

Check a reconstruction job's status, OpenXML metrics, and token/cost usage by jobId, then optionally download the completed .pptx or a slide preview PNG.

Instructions

Inspect status, OpenXML object metrics, and token/cost usage ledger for a reconstruction jobId, and optionally download its .pptx or preview PNG.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jobId": "<jobId>"
    },
    "name": "decken_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
outputPathNoOptional path to save the completed .pptx binary.
previewSlideIdNoOptional slideId to download its preview PNG.
previewOutputPathNoDestination path for previewSlideId PNG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the read-oriented scope plus an optional file-writing download. It omits whether downloading overwrites an existing outputPath, whether the job must be finished, permission requirements, and what happens on invalid jobIds. It adds real behavioral context but leaves safety-relevant gaps for a tool that can write files.

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 lists the inspection outputs first and the optional download last, so the primary purpose is immediately clear. It is dense but not padded, with only a slight run-on quality.

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?

For a four-parameter tool with no annotations and no output schema, the description adequately states what the response contains (status, metrics, ledger). It falls short on error behavior, completion prerequisites, and download overwrite semantics, which an agent would need before calling it on an arbitrary jobId.

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

Parameters3/5

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

Schema coverage is 75%, so most parameters are already described. The description adds that jobId refers to a reconstruction job and clarifies outputPath is for the .pptx while previewSlideId triggers a PNG, but it does not explain jobId format or the dependency between previewSlideId and previewOutputPath. Baseline 3 is appropriate given the schema does most of the work.

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, "Inspect," and names the resources returned: status, OpenXML object metrics, and token/cost usage ledger, scoped to a reconstruction jobId. It also covers the optional download capability, so an agent knows exactly what the tool does, though it never names a sibling to differentiate against (e.g., decken_list_jobs).

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 only implied: fetch a jobId for inspection. The description says downloads are optional but gives no guidance on when to inspect versus list jobs, no prerequisites (e.g., job must be complete), and no exclusions. An agent can infer the basic context but must guess at alternatives.

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