Skip to main content
Glama

PackDesk

diagnose_coding_fault

Diagnose a packaging/coding/marking printer fault code and return the normalised row (meaning, likely causes, checks, parts, consumables) with sources.

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": {
      "brand": "<brand>",
      "code": "<code>"
    },
    "name": "diagnose_coding_fault"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe fault code or message shown on the printer
brandYes
modelNoOptional model or series
symptomNoOptional free-text symptom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the return payload (meaning, causes, checks, parts, consumables, sources), which is useful, but says nothing about whether the lookup is read-only, what happens on a miss, whether results are cached/curated, or confidence/coverage per brand.

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?

One front-loaded sentence with the verb and output contents up front and no filler. The parenthetical list is dense but each item earns its place by pre-announcing the return fields.

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?

No output schema exists, and the description compensates by enumerating the returned fields plus sources, which is the key thing an agent needs. Remaining gaps are minor: no guidance on unmatched codes and no note that only Domino/Videojet are supported.

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 description coverage is 75%, with code, model and symptom documented and brand constrained by an enum, so the schema does most of the work. The description adds no meaning beyond it, e.g. what format 'code' should take or how model/symptom change the result.

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?

Specific verb ("Diagnose") plus resource ("fault code") scoped to packaging/coding/marking printers, and it names the returned fields. It does not differentiate itself from the sibling lookup_code, so an agent must infer whether this is the richer/diagnostic variant.

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: it is clear you call it when you have a fault code from a printer, but there is no explicit when-to-use/when-not, no mention of lookup_code as the alternative, and no statement about coverage limits or behavior when a code is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources