Skip to main content
Glama

Electronics Architect

Derating analysis

run_derating
Read-onlyIdempotent

Grade every rated part of a design against a derating standard — NASA GSFC (EEE-INST-002 Table 4 by part family: ICs at 0.75 × Tmax, never above 110 °C or Tmax − 40; diodes at 0.80 × Tmax, never above 125 °C or Tmax − 40) or IPC-9592 (115 °C cap) — after one nominal solve. Solved server-side through the signed-in account: unmetered on Pro and Team; on the Free plan each solve counts toward its 10 a month through connected apps (meta.solvesRemaining says how many are left), and a design has 1 sheet. The same evaluator the editor's Derating panel runs, so the person sees exactly this report. Give a design document, a templateId or a saved design's designId, and the standard (required: which table a part is held to is the engineer's call). Returns, per graded component, its stress checks — parameter, actual, rated, the derated limit, stressPct (actual over RATED), status and basis (the EEE-INST-002 section the rule comes from, or null for a check the standard does not cover and for every IPC check, which is unverified) — its worst status and mitigation text; summary counts compliant / warning / overstressed; thresholds is the factor table used. Status: GREEN inside the limit, ORANGE within the last 20 % under it, RED over it. A rating left at 0 or blank is UNSTATED, not a 0 limit: the parameter is skipped and named in the component's unrated list — tell the engineer what to enter rather than reporting a pass. Sources, loads and the BMS have no abs-max ratings and are not graded. A Motor's "Rated Power" check grades SHAFT power (electrical input × efficiency) against ratedPower, its rated mechanical output; an Inverter's "VA Loading" grades its output apparent power against vaRating. Read solve.converged first: a report on a solve that did not converge grades numbers that mean nothing. Unmetered on Pro and Team; on the Free plan it counts as one of the month's solves.

Input Schema

NameRequiredDescriptionDefault
designNoThe design document. Give this, `templateId` or `designId`.
designIdNoA saved design's id from create_design or list_designs — needs the signed-in account. Give this, `design` or `templateId`.
standardYesThe derating standard to grade against. Required.
templateIdNoA shipped template id from list_templates. Give this, `design` or `designId`.
ambientTemperatureNoAmbient in °C for the solve and the thermal stress figure. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantial context beyond that: server-side execution, Pro/Team unmetered versus Free-plan solve accounting with meta.solvesRemaining, the 1-sheet limit, which elements are not graded (sources, loads, BMS), UNSTATED handling for 0/blank ratings, GREEN/ORANGE/RED thresholds, and Motor/Inverter check semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and almost every sentence carries real information, but the passage is a ~350-word wall of text and the plan metering is literally stated twice ('Unmetered on Pro and Team; on the Free plan...'). Trimming the duplication and tightening the edge-case list would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a tool with no output schema: it describes each returned element (stress checks, limit, stressPct, status, basis, worst status, mitigation, summary, thresholds), plus the convergence caveat, ungraded element types, and metering behavior. Nothing material an agent needs to call or interpret it is missing.

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 100%, so all five parameters are already documented. The description only marginally extends this, adding that the standard choice is 'the engineer's call' and reiterating the design/templateId/designId alternatives; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Grade every rated part of a design against a derating standard'), names the two supported standards with per-family factors, and is clearly distinguishable from siblings like solve_design, validate_design and review_design. An agent can tell what this returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the precondition ('after one nominal solve') and the input alternatives (design document, templateId, or designId), and instructs to check solve.converged before reading the report. It never explicitly contrasts itself with sibling tools such as validate_design or review_design, so the routing guidance is implied rather than spelled out.

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