Skip to main content
Glama

BRAINIAC Manufacturing Quality

Classify manufacturing defects

manufacturing-quality_defect-classify

Classify failed inspections with transparent token rules such as dimensional, surface, assembly, material, or functional. Classification is not a certification. Price $0.04 USDC. POST /api/v1/manufacturing-quality/defect-classify. Unpaid calls return 402 and do not run.

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": "manufacturing-quality_defect-classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
batchesNo
evidenceNo
minSampleNo
standardsNo
thresholdsNo
inspectionsNo
measurementsNo
spcMinSampleNo
defectRateThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add real behavioral facts: fixed price of $0.04 USDC, POST transport, and that unpaid calls return 402 without executing. The 'transparent token rules' and 'not a certification' statements also set expectations about determinism and output meaning. What is missing is any disclosure of response format or what happens with partially populated inputs across the 13 optional parameters.

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?

Four short sentences, front-loaded with the capability and followed by caveat, price, endpoint, and payment failure behavior. Nothing is wasted, though the endpoint path and payment sentence are more operational than semantic.

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?

For a tool with 13 optional nested parameters, nested objects, no output schema, and no annotations, the description explains almost nothing about the input contract. Commercial and transport details are covered, but an agent cannot confidently construct a correct payload from this definition alone.

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

Parameters1/5

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

There are 13 parameters with 0% schema description coverage, including non-obvious ones like inspections, measurements, standards, thresholds, minSample, spcMinSample, and defectRateThreshold. The description mentions none of them, so an agent gets no help mapping intent to fields or understanding units, formats, or precedence among the csv/json/text/file alternatives.

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 ('Classify failed inspections') and enumerates the classification categories (dimensional, surface, assembly, material, functional), which tells an agent what the tool produces. It does not explicitly contrast itself with siblings like defect-rate-calculate or nonconformance-report-generate, so differentiation is left to the reader.

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 context is implied by 'failed inspections' and a scope boundary is drawn with 'Classification is not a certification,' which is useful exclusions guidance. However, there is no explicit statement of when to use this versus the sibling analysis/report tools, and no prerequisite or input-shape guidance.

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