Skip to main content
Glama

BRAINIAC Manufacturing Quality

Calculate defect rate

manufacturing-quality_defect-rate-calculate

Calculate defect rate from decided pass/fail inspections and compare it with an explicitly supplied threshold. Small samples are disclosed. Price $0.04 USDC. POST /api/v1/manufacturing-quality/defect-rate-calculate. 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-rate-calculate"
  }
}

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
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the pricing model ($0.04 USDC), the 402 unpaid-call behavior, and that small samples are flagged in the response. It does not say whether the call is read-only and side-effect free, or how the returned comparison is structured, leaving key behavioral facts unstated 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 tight sentences, front-loaded with the core action, then sample-size behavior, then commercial/transport details. Nothing is padded, but the endpoint path and price could arguably be moved to metadata rather than prose.

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?

Placeholder.

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, so the description must compensate and it largely does not. It hints at two inputs only — the inspections/result 'decided pass/fail' data and the 'explicitly supplied threshold' — while batches, measurements, standards, evidence, minSample, spcMinSample, csv/json/file/text payloads remain entirely undocumented.

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 ('Calculate defect rate') plus the input scope ('decided pass/fail inspections') and the comparison action against a threshold. It is clearly distinguishable from siblings like batch-compare or nonconformance-report-generate, though it never names an alternative.

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?

'from decided pass/fail inspections' and 'explicitly supplied threshold' imply prerequisites (inspections must already be decided; the threshold must come from the caller rather than being inferred). There is no explicit when-to-use/when-not guidance or routing to a sibling, so usage is only implied.

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