Skip to main content
Glama

Whatic IC Datasheets

by io.whatic
OverviewDiscussionsAdmin

Shortlist ICs by spec

find_parts
Read-onlyIdempotent

Shortlist IC part numbers by parametric spec constraints, ranked by how many constraints each part satisfies, then by headroom past those thresholds, and spread across device families. Each constraint is {canonical, op: gte|lte|eq|range, value, unit?}. Returns per-constraint pass/fail/unknown, plus matched (parts meeting EVERY constraint), ranked (all parts scored, partial matches included) and returned (parts in this response). truncated means some qualifying parts are not on this page. When matched is 0 every result is a partial match. canonical MUST be one of the exact (case-sensitive) names enumerated in this tool's inputSchema, also readable as the whatic://parametric/canonicals resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNoMaximum number of parts to return, best first.
constraintsYesSpec constraints; a part is ranked by how many it satisfies.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / Constraint / properties / canonical / description
      Previous value: -"Canonical parameter name (see the whatic://parametric/canonicals resource or this tool's description for the exact set), e.g. supply_voltage_range."New value: +"Canonical parameter name, e.g. supply_voltage_range — must be one of the values enumerated for this field (also readable as the whatic://parametric/canonicals resource)."
  2. Changed1 schema field changed
    • changedInput schema / $defs / Constraint / properties / canonical / enum
      Previous value: -[
-  "abs_max_current",
-  "abs_max_voltage",
-  "adc_resolution",
-  "block_erase_time",
-  "breakdown_voltage_ds",
-  "channel_count",
-  "clamping_voltage",
-  "clock_frequency",
-  "cmrr",
-  "cmti",
-  "coil_power",
-  "coil_resistance",
-  "coil_voltage",
-  "collector_emitter_voltage",
-  "contact_current",
-  "contact_resistance",
-  "core_size",
-  "cpu_speed",
-  "current_rating",
-  "dark_current",
-  "data_rate",
-  "data_retention",
-  "dc_resistance",
-  "drain_current",
-  "driver_count",
-  "dropout_voltage",
-  "dynamic_range",
-  "eeprom_size",
-  "emitter_base_voltage",
-  "fall_time",
-  "forward_current",
-  "forward_voltage",
-  "gain_bandwidth",
-  "gate_charge",
-  "impedance",
-  "input_bias_current",
-  "input_capacitance",
-  "input_offset_current",
-  "input_offset_current_drift",
-  "input_offset_voltage",
-  "input_offset_voltage_drift",
-  "input_voltage_noise_density",
-  "insertion_loss",
-  "io_count",
-  "isolation_voltage",
-  "junction_capacitance",
-  "load_capacitance",
-  "memory_size",
-  "operate_time",
-  "operating_frequency",
-  "operating_temperature",
-  "output_capacitance",
-  "output_count",
-  "output_current",
-  "output_noise_voltage",
-  "output_power",
-  "output_voltage",
-  "output_voltage_high",
-  "output_voltage_low",
-  "page_program_time",
-  "peak_pulse_current",
-  "power_dissipation",
-  "program_erase_cycles",
-  "program_memory_size",
-  "propagation_delay",
-  "psrr",
-  "quiescent_current",
-  "ram_size",
-  "rds_on",
-  "receiver_count",
-  "rectified_current",
-  "release_time",
-  "response_time",
-  "reverse_leakage_current",
-  "reverse_recovery_time",
-  "reverse_transfer_capacitance",
-  "reverse_voltage",
-  "rise_time",
-  "sample_rate",
-  "sensitivity",
-  "settling_time",
-  "slew_rate",
-  "standby_current",
-  "supply_voltage_range",
-  "switching_frequency",
-  "switching_voltage",
-  "vgs_threshold",
-  "zener_voltage"
-]New value: +[
+  "abs_max_current",
+  "abs_max_voltage",
+  "adc_resolution",
+  "block_erase_time",
+  "breakdown_voltage_ds",
+  "channel_count",
+  "clamping_voltage",
+  "clock_frequency",
+  "cmrr",
+  "cmti",
+  "coil_power",
+  "coil_resistance",
+  "coil_voltage",
+  "collector_emitter_voltage",
+  "contact_current",
+  "contact_resistance",
+  "core_size",
+  "cpu_speed",
+  "current_rating",
+  "dark_current",
+  "data_rate",
+  "data_retention",
+  "dc_resistance",
+  "drain_current",
+  "driver_count",
+  "dropout_voltage",
+  "dynamic_range",
+  "eeprom_size",
+  "emitter_base_voltage",
+  "fall_time",
+  "forward_current",
+  "forward_voltage",
+  "gain_bandwidth",
+  "gate_charge",
+  "impedance",
+  "input_bias_current",
+  "input_capacitance",
+  "input_offset_current",
+  "input_offset_current_drift",
+  "input_offset_voltage",
+  "input_offset_voltage_drift",
+  "input_voltage_noise_density",
+  "insertion_loss",
+  "io_count",
+  "isolation_voltage",
+  "junction_capacitance",
+  "load_capacitance",
+  "memory_size",
+  "operate_time",
+  "operating_frequency",
+  "operating_temperature",
+  "output_capacitance",
+  "output_count",
+  "output_current",
+  "output_noise_voltage",
+  "output_power",
+  "output_voltage",
+  "output_voltage_high",
+  "output_voltage_low",
+  "page_program_time",
+  "peak_pulse_current",
+  "power_dissipation",
+  "program_erase_cycles",
+  "program_memory_size",
+  "propagation_delay",
+  "psrr",
+  "quiescent_current",
+  "ram_size",
+  "rds_on",
+  "receiver_count",
+  "rectified_current",
+  "release_time",
+  "response_time",
+  "reverse_leakage_current",
+  "reverse_recovery_time",
+  "reverse_transfer_capacitance",
+  "reverse_voltage",
+  "rise_time",
+  "sample_rate",
+  "sector_erase_time",
+  "sensitivity",
+  "settling_time",
+  "slew_rate",
+  "standby_current",
+  "supply_voltage_range",
+  "switching_frequency",
+  "switching_voltage",
+  "vgs_threshold",
+  "zener_voltage"
+]
  3. Changed1 schema field changed
    • addedInput schema / $defs / Constraint / properties / canonical / enum
      Added value: +[
+  "abs_max_current",
+  "abs_max_voltage",
+  "adc_resolution",
+  "block_erase_time",
+  "breakdown_voltage_ds",
+  "channel_count",
+  "clamping_voltage",
+  "clock_frequency",
+  "cmrr",
+  "cmti",
+  "coil_power",
+  "coil_resistance",
+  "coil_voltage",
+  "collector_emitter_voltage",
+  "contact_current",
+  "contact_resistance",
+  "core_size",
+  "cpu_speed",
+  "current_rating",
+  "dark_current",
+  "data_rate",
+  "data_retention",
+  "dc_resistance",
+  "drain_current",
+  "driver_count",
+  "dropout_voltage",
+  "dynamic_range",
+  "eeprom_size",
+  "emitter_base_voltage",
+  "fall_time",
+  "forward_current",
+  "forward_voltage",
+  "gain_bandwidth",
+  "gate_charge",
+  "impedance",
+  "input_bias_current",
+  "input_capacitance",
+  "input_offset_current",
+  "input_offset_current_drift",
+  "input_offset_voltage",
+  "input_offset_voltage_drift",
+  "input_voltage_noise_density",
+  "insertion_loss",
+  "io_count",
+  "isolation_voltage",
+  "junction_capacitance",
+  "load_capacitance",
+  "memory_size",
+  "operate_time",
+  "operating_frequency",
+  "operating_temperature",
+  "output_capacitance",
+  "output_count",
+  "output_current",
+  "output_noise_voltage",
+  "output_power",
+  "output_voltage",
+  "output_voltage_high",
+  "output_voltage_low",
+  "page_program_time",
+  "peak_pulse_current",
+  "power_dissipation",
+  "program_erase_cycles",
+  "program_memory_size",
+  "propagation_delay",
+  "psrr",
+  "quiescent_current",
+  "ram_size",
+  "rds_on",
+  "receiver_count",
+  "rectified_current",
+  "release_time",
+  "response_time",
+  "reverse_leakage_current",
+  "reverse_recovery_time",
+  "reverse_transfer_capacitance",
+  "reverse_voltage",
+  "rise_time",
+  "sample_rate",
+  "sensitivity",
+  "settling_time",
+  "slew_rate",
+  "standby_current",
+  "supply_voltage_range",
+  "switching_frequency",
+  "switching_voltage",
+  "vgs_threshold",
+  "zener_voltage"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral detail: the exact return fields (per-constraint pass/fail/unknown, matched, ranked, returned), the meaning of truncated, and the special case when matched=0. This goes well beyond the annotations and gives the agent a precise model of what to expect.

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 compact yet information-dense. The first sentence captures the core purpose and ranking logic. Subsequent sentences define the output fields and edge cases. No fluff, no repetition, and the most critical constraint (canonical naming) is placed near the end but still earns its place. The structure front-loads the key behavior.

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?

The tool has a complex input schema (nested constraint object with enum canonicals) and an output schema (not shown but exists). The description explains the ranking algorithm, the meaning of each output field, the 'truncated' flag, and the partial-match behavior. It also references a resource for canonical names. For an agent, everything needed to call this tool correctly and interpret results is present.

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

Parameters4/5

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

Schema coverage is 100% and each parameter already has a description. The description adds a few useful extras: it explicitly warns that 'canonical' must be one of the exact case-sensitive names enumerated in the schema, and points to a canonical resource for reference. It also clarifies that 'unit' is informational only and comparisons use the stored SI value. These augment the schema meaningfully without redundancy.

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 specific verb ('Shortlist') and resource ('IC part numbers') plus the exact mechanism ('by parametric spec constraints'). It also distinguishes the tool from siblings by explaining the ranking behavior (how many constraints satisfied, headroom, family spread). This is far more specific than a generic 'search' and clearly differentiates it from compare_parts or search.

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?

The description clearly states the tool is for parametric spec-based shortlisting, and explains the output semantics (matched, ranked, returned, truncated). It does not explicitly name alternative tools or say when NOT to use it, but the context strongly implies this is the go-to for constraint-based filtering. It lacks explicit exclusion guidance but is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Whatic IC Datasheets toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources