Skip to main content
Glama

BRAINIAC Manufacturing Quality

Check production tolerances

manufacturing-quality_production-tolerance-check

Compare supplied measurements with caller-supplied lower and upper limits. SPC mean±3σ limits are computed only when the disclosed observation minimum is met. Price $0.05 USDC. POST /api/v1/manufacturing-quality/production-tolerance-check. 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_production-tolerance-check"
  }
}

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, the description does carry real behavioral weight: it discloses the $0.05 USDC price, the POST endpoint, that unpaid calls return 402 and do not execute, and that SPC limits are computed only when the observation minimum is met. It does not disclose what the tool does with the batches, inspections, evidence, or thresholds inputs, or what the response contains, so the disclosure is partial for a 13-parameter tool.

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 core operation before the conditional SPC rule, pricing, and transport details. Nothing is padded, though the raw endpoint path is of limited value to an agent choosing whether to call it.

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 parameters, nested objects, no annotations, and no output schema, the description leaves most of the calling contract unstated. An agent cannot tell from this text what the non-tolerance parameters are for or what a successful result looks like.

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?

Schema description coverage is 0% across 13 parameters including nested objects. The description adds meaning for only a few: measurements, the lower/upper limits in standards, and the observation minimum (minSample/spcMinSample). The purpose of batches, inspections, evidence, thresholds, defectRateThreshold, and the four text/file/csv/json input variants is left entirely unexplained.

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 supplied measurements against caller-supplied lower/upper limits, plus SPC mean±3σ limit computation. That is far more informative than the title. It does not differentiate from siblings such as defect-rate-calculate or batch-compare, and the described scope covers only part of a 13-parameter tool.

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?

No when-to-use or when-not-to-use guidance and no named alternative. The description never says which of the four input channels (csv, file, json, text) to choose, nor when the batches/inspections/evidence payloads are needed versus a simple measurement list.

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