Skip to main content
Glama
pitkonst

@whatic/mcp

by pitkonst
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

find_parts

Shortlist IC part numbers by parametric constraints, ranked by the number of specs each part satisfies. Returns per-constraint pass/fail/unknown to identify matching components.

Instructions

Shortlist IC part numbers by parametric spec constraints, ranked by how many constraints each part satisfies. Each constraint is {canonical, op: gte|lte|eq|range, value, unit?}. Returns per-constraint pass/fail/unknown. canonical MUST be one of the exact names below (case-sensitive): 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

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

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the ranking criterion, return granularity (per-constraint pass/fail/unknown), and the strict case-sensitive canonical requirement. It does not explain error behavior or the meaning of 'unknown', but the core behavior is transparent.

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?

The opening two sentences are concise and front-loaded with purpose and behavior. However, the description includes a very long canonical-name list that duplicates the schema enum, making the overall description unnecessarily large.

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?

The description is mostly complete for a parametric search tool: it explains the constraint model, ranking behavior, and return granularity. Minor gaps like the meaning of 'unknown' and tie-breaking are not blocking for correct invocation.

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 the baseline is 3. The description adds a compact constraint structure overview and an explicit case-sensitivity warning, but the large canonical list duplicates the schema enum and adds little beyond what the schema already provides.

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 states a specific verb ('Shortlist'), a clear resource ('IC part numbers'), and a distinguishing method ('by parametric spec constraints'). This clearly separates it from generic search/lookup sibling tools even without naming them.

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?

It clearly conveys when to use the tool: when the agent wants to filter/shortlist parts by parametric constraints and rank by constraint satisfaction. However, it does not explicitly list when not to use it or name alternatives such as search or lookup.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pitkonst/whatic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server