Skip to main content
Glama

BRAINIAC Manufacturing Quality

Compare batch quality

manufacturing-quality_batch-compare

Compare batch defect rates only when each batch meets the disclosed sample minimum. Rate differences are not treated as regulatory findings. Price $0.05 USDC. POST /api/v1/manufacturing-quality/batch-compare. 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_batch-compare"
  }
}

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

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does useful work: it discloses cost ($0.05 USDC), the 402-on-unpaid behavior, and that failed payments do not run the comparison, plus a caveat that rate differences are not regulatory findings. It omits the output shape and how the sample-minimum gate behaves when batches fail it, which keeps it below a 5.

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?

Front-loads the key constraint and caveat before the pricing and transport boilerplate, and every sentence is doing work. The endpoint/payment sentences are terse and functional rather than padded.

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 13-parameter tool with deeply nested objects, no annotations, and no output schema, the description leaves the entire input model unexplained and does not describe the comparison result. An agent could not construct a valid payload from this description alone.

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?

13 parameters at 0% schema description coverage, and the description explains only the sample-minimum concept (minSample). It says nothing about the four alternative payload channels (csv/file/json/text), batches, inspections, measurements, standards, thresholds, evidence, spcMinSample, or defectRateThreshold, so the schema gaps are not compensated.

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 — 'Compare batch defect rates' — which an agent can distinguish from defect-rate-calculate or report-generate. It does not explicitly name a sibling to disambiguate against, so it stops short of a 5.

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?

Gives a real precondition ('only when each batch meets the disclosed sample minimum'), which is genuine when-to-use guidance. It never says when NOT to use it versus the defect-rate or report siblings, so usage is only implied by the comparison framing.

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