Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WHATIC_MCP_URLNoOverride the remote MCP server URL. Defaults to https://whatic.io/mcp.https://whatic.io/mcp

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_partsA

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 that qualified) vs returned (parts in this response) — when they differ this is a ranked page, not the full set. 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

get_specsA

Read canonical extracted specs (min/typ/max, unit, conditions) for known IC part numbers from a pre-extracted parametric index — not from datasheet text. This is the cheapest and most precise source for numeric parameters where it has coverage. Optionally restrict to specific canonical parameter names. A part absent from results (with a "No specs found" warning) means no index coverage, not that the datasheet lacks the parameter — fall back to lookup for that part.

compare_partsA

Relative price tier, stock posture, and library class for a set of IC part numbers (a ranking from a distributor snapshot, not a live quote).

searchA

Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque ref). Pass a ref list to get_segments for full content. If you already know the part number(s), prefer lookup — it fuses this search with get_segments in one call and groups full content per part. Use search when the part is unknown, or to triage snippets before pulling full content. For part-specific queries, pass scope='device:' (e.g. scope='device:NE5532') to restrict hits to that part and avoid cross-part contamination.

lookupA

One-shot spec/section retrieval: full content of the most relevant datasheet segments for one or more parts (fuses search+get_segments). Already groups results per part (via parts), so prefer lookup over search when you know the part(s).

get_segmentsA

Expand opaque ref tokens (from search/lookup) into full datasheet segment content.

get_imageA

Fetch datasheet figure images (PNG/JPEG) for opaque ref tokens obtained from search/lookup/get_segments. Returns each image plus its caption/description/page metadata. Only type='image' segments have image data; a ref that is not one comes back as an error record whose available_images lists the document's figures nearest that ref's page and section, closest first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation4/5

find_parts, get_specs, compare_parts, and get_image are clearly distinct, while search, lookup, and get_segments overlap in the retrieval workflow but have explicit descriptions that differentiate triage, fused retrieval, and ref expansion. Minor boundary ambiguity remains between get_specs and lookup, but the descriptions provide enough guidance.

Naming Consistency4/5

Most tools follow a predictable verb_noun pattern: find_parts, get_specs, compare_parts, get_segments, get_image. The bare-verb names search and lookup are minor deviations that remain readable and do not obscure their purpose.

Tool Count5/5

Seven tools form a well-scoped toolkit for IC parametric discovery and datasheet retrieval. Each tool earns its place by covering a distinct step in the workflow without unnecessary duplication or bloat.

Completeness5/5

The toolset covers the full read-only datasheet research lifecycle: parametric discovery, normalized spec lookup, distributor comparison, corpus search, full segment retrieval, and figure extraction. There are no obvious dead ends or missing operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues