Skip to main content
Glama

check_design_fit

Read-only

Validate whether a component will work within your operating conditions. Compares your design parameters against the datasheet's absolute maximum ratings and recommended operating conditions. Returns PASS/FAIL/WARNING per parameter with margin percentages.

Parameter mapping by component type:

  • Buck/boost converters: input_voltage, output_voltage, output_current, ambient_temp

  • MOSFETs: supply_voltage=VDS, output_current=ID (drain current), ambient_temp

  • LDOs: input_voltage, output_voltage, output_current, ambient_temp

  • Logic ICs: supply_voltage=VCC, ambient_temp

Result semantics (per-parameter 'result' field):

  • PASS: comfortable margin. For a recommended-operating RANGE, any value inside the range (including the exact edges) is PASS. For an absolute-MAX rating, PASS means more than 10% below the limit.

  • WARNING: for absolute-max ratings only, the user value is within 10% of the limit (but not over) — part will work but with thin margin for part-to-part variation, temperature drift, and transients. Consider derating.

  • FAIL: user value is outside the allowed range / exceeds the limit — part is out of spec and will be stressed or damaged.

  • INSUFFICIENT_DATA: the check could not be completed safely — most commonly an ambient_temp input that could not be translated to a junction-temperature check (see the temperature note below). INSUFFICIENT_DATA never counts as a PASS: it pulls the overall verdict down to at-least-WARNING. Each check also reports 'limit_type' (max / min / range / fixed) so you can see whether it was judged against an operating range, an absolute-max rating, or a fixed-output setpoint.

Temperature honesty:

  • ambient_temp is NOT silently treated as a junction temperature. The stored operating-temperature limit is junction-suspect, so a bare ambient input is never reported as a clean PASS on thermal grounds. If you also supply input_voltage, output_voltage and output_current AND a thermal-resistance (RthJA) value is available, the tool estimates Tj = Ta + Pd·RthJA (Pd ≈ (Vin-Vout)·Iout, a documented approximation) and checks the junction estimate — reported as 'temperature (junction est.)' with the assumptions in the note. Otherwise the temperature check returns INSUFFICIENT_DATA asking you to pull RthJA via read_datasheet. The 'temperature_basis' field (junction / ambient / unknown) tells you which basis was used.

Behavior:

  • Two-tier validation. For parameters in our structured database (Vin, Iout, operating temp, etc.), returns instantly and free of LLM cost. For parameters only found in the datasheet text, falls back to an LLM read of the absolute-max and recommended-operating-conditions sections. The 'validation_method' field in the response tells you which path was used.

  • If the part hasn't been extracted yet and the LLM fallback is needed, this call triggers extraction (30s-2min). Returns status='extracting' if so — poll check_extraction_status and retry.

When NOT to use:

  • You need power dissipation or junction-temperature rise — this tool only checks nameplate limits. Pull RthJA from read_datasheet and calculate yourself.

  • You need SOA (safe-operating-area) curve checks for MOSFETs — use analyze_image on the SOA graph.

  • You're checking a passive or mechanical part with no abs-max table — there's nothing for this tool to compare against.

Example: check_design_fit('TPS54302', input_voltage=24, output_current=2.5, ambient_temp=70)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
part_numberYesSpecific manufacturer part number to validate. Not a value or description.
ambient_tempNoAmbient temperature TA (°C).
input_voltageNoInput voltage / VIN (V). For converters.
output_currentNoOutput current / IOUT (A). For MOSFETs, this is drain current ID.
output_voltageNoOutput voltage / VOUT (V). For converters/LDOs.
supply_voltageNoSupply voltage / VCC / VDD (V). For MOSFETs, this is VDS (drain-source voltage). NOT used for power dissipation — compared against VDS(max) only.
switching_frequencyNoSwitching frequency FSW (kHz). For converters.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changed
    • addedInput schema / properties / ambient_temp / maximum
      Added value: +200
    • addedInput schema / properties / ambient_temp / minimum
      Added value: +-65
    • addedInput schema / properties / input_voltage / maximum
      Added value: +1500
    • addedInput schema / properties / input_voltage / minimum
      Added value: +0
    • addedInput schema / properties / output_current / maximum
      Added value: +500
    • addedInput schema / properties / output_current / minimum
      Added value: +0
    • addedInput schema / properties / output_voltage / maximum
      Added value: +1500
    • addedInput schema / properties / output_voltage / minimum
      Added value: +0
    • addedInput schema / properties / supply_voltage / maximum
      Added value: +1500
    • addedInput schema / properties / supply_voltage / minimum
      Added value: +0
    • addedInput schema / properties / switching_frequency / maximum
      Added value: +10000000
    • addedInput schema / properties / switching_frequency / minimum
      Added value: +0
  2. Changed6 schema fields changed
    • changedInput schema / properties / ambient_temp / description
      Previous value: -"Ambient temperature (C)"New value: +"Ambient temperature TA (°C)."
    • changedInput schema / properties / input_voltage / description
      Previous value: -"Input voltage (V)"New value: +"Input voltage / VIN (V). For converters."
    • changedInput schema / properties / output_current / description
      Previous value: -"Output current (A)"New value: +"Output current / IOUT (A). For MOSFETs, this is drain current ID."
    • changedInput schema / properties / output_voltage / description
      Previous value: -"Output voltage (V)"New value: +"Output voltage / VOUT (V). For converters/LDOs."
    • changedInput schema / properties / supply_voltage / description
      Previous value: -"Supply voltage (V)"New value: +"Supply voltage / VCC / VDD (V). For MOSFETs, this is VDS (drain-source voltage). NOT used for power dissipation — compared against VDS(max) only."
    • changedInput schema / properties / switching_frequency / description
      Previous value: -"Switching frequency (kHz)"New value: +"Switching frequency FSW (kHz). For converters."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description reveals non-obvious behaviors: two-tier validation (structured DB vs LLM fallback), side-effect of triggering extraction with a 30s-2min delay, honest temperature handling (not silently treating ambient as junction), and explicit result semantics (PASS/WARNING/FAIL/INSUFFICIENT_DATA). No contradiction with annotations.

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

Conciseness5/5

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

The description is structured with clear section headers (Parameter mapping, Result semantics, Temperature honesty, Behavior, When NOT to use), front-loads the core purpose, and includes an illustrative example. Every sentence adds unique information, and the length is proportional to the tool's complexity.

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?

Given the absence of an output schema, the description thoroughly explains return fields (result, limit_type, validation_method, temperature_basis) and covers all parameter semantics, edge cases (INSUFFICIENT_DATA), and side effects. It is self-contained for safe and effective use, including limitations and alternatives.

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

Parameters5/5

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

Even though schema description coverage is 100%, the description adds significant layer-valued context: component-type-to-parameter mapping (Buck/boost, MOSFET, LDO, Logic ICs), clarification that supply_voltage maps to VDS for MOSFETs, and the distinction between ambient_temp and junction-temperature estimation. This goes far beyond the literal schema definitions.

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?

The description opens with a precise verb ('Validate whether a component will work within your operating conditions') and clearly states the comparison against datasheet absolute maximum ratings and recommended operating conditions. It distinguishes itself from sibling tools like read_datasheet and analyze_image by defining its unique role in design validation, reinforced by an example.

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

Usage Guidelines5/5

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

The 'When NOT to use' section explicitly lists three exclusion scenarios with alternative tools (power dissipation → read_datasheet, SOA curves → analyze_image, passive/mechanical parts → no tool). It also explains when to use the tool (validating design parameters) and provides process guidance on handling the 'extracting' status through check_extraction_status.

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.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search_parts finds parts, search_datasheets searches extracted content, read_datasheet reads sections, analyze_image extracts visual data, compare_parts batches comparisons, find_alternative finds substitutes, check_design_fit validates specs, prefetch/check/manage extraction status, and request/confirm handle uploads. The descriptions cross-reference each other to further eliminate ambiguity.

Naming Consistency5/5

All 12 tools follow the verb_noun snake_case pattern consistently (analyze_image, check_design_fit, compare_parts, prefetch_datasheets, request_datasheet_upload, etc.). No mixing of camelCase, verb styles, or vague generic names.

Tool Count5/5

12 tools is ideal for a datasheet-centric server, covering the full workflow from part discovery and datasheet extraction to analysis, validation, comparison, and upload. The count is neither bloated nor thin, and every tool earns its place.

Completeness5/5

The tool surface is comprehensive for the domain: part search, spec-based semantic search, detailed part data, datasheet reading (section/search), image analysis, design-fit checking, part comparison, alternative finding, extraction lifecycle management, and manual datasheet upload (request+confirm). No obvious dead ends or critical missing operations.