Skip to main content
Glama

match_components

Read-onlyIdempotent

Reverse search over a typed spec layer: pass a category and engineering requirements, get every catalogued item grouped as A (meets all stated requirements), B (fails a named requirement, both figures quoted) or C (could fit, data missing). Verdicts cite the datasheet page. Omit parameters you do not care about. Categories: reaction-wheels, star-trackers, obc-computers, batteries, radios, solar-panels, propulsion, sun-sensors, magnetometers, magnetorquers, imus-gyros, gnss-receivers, eps, deployers, thermal, antennas, sdr-modems, cameras, structures, platforms, ground-stations, sadm, tanks-valves, separation-systems, pointing-mechanisms, test-facilities (environmental test labs — items are companies: test, shaker_min_kn, tvac_min_m, specimen_min_kg, emc_min_m). The answer is compact: group A in full (up to 25), groups B and C — the first 10 with the reason, plus counts and the fields most often unpublished in C; page with group and offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bandNoradio: frequency band UHF|VHF|S|X|L|C|Ku|Ka
testNotest-facilities: kinds of test the lab must ALL offer, comma-separated — vibration, shock, thermal-vacuum, thermal, emc, radiation, acoustic, magnetic, rf-antenna, mass-properties, outgassing, optical
bus_vNoyour power bus voltage, V — the unit must accept it
groupNopage through one group only — use with offset from paging.next
limitNoitems of groups B and C to return (default 10, max 50); group A comes in full up to 25
mediaNotank/valve: propellant/media, e.g. xenon, hydrazine
orbitNoplatforms: orbit the bus is designed for — LEO | SSO | VLEO | MEO | GEO | HEO | lunar | deep space (LEO, SSO and VLEO pass each other)
exportNorequired export status: ITAR-free | EAR99 | ITAR
form_uNostructures / platforms: CubeSat size, U (exact match)
offsetNostart position inside the group (paging.next.offset of the previous answer)
acq_maxNostar trackers: max lost-in-space acquisition time, s
arw_maxNoIMU: worst angle random walk, deg per sqrt hour
data_ifNorequired data interface: CAN, RS-422, RS-485, SpaceWire, I2C, SPI, UART, MIL-STD-1553
mpx_minNocamera: min sensor resolution, Mpx
ram_minNoOBC: min RAM, MB
tid_minNoany category: min radiation tolerance TID, krad
categoryNowhich component class to search — ONE per call; for several classes call once per class (default reaction-wheels)
lead_maxNomax lead time, months
mass_maxNomax unit mass, grams
mass_minNomin unit mass, grams (rare: "heavier than")
materialNostructure: alloy, e.g. Al 7075
ttff_maxNoGNSS: worst cold TTFF, s
bands_minNocamera: min spectral bands
clock_minNoOBC: min CPU clock, MHz
dv_min_msNoplatforms / propulsion: min delta-v, m/s
emc_min_mNotest-facilities: min test-article size the EMC / anechoic chamber takes, m
gsd_max_mNocamera: worst ground sample distance, m
isp_min_sNopropulsion: min specific impulse, s
link_bandNoplatforms: radio band of the bus — UHF | VHF | L | S | X | Ku | Ka | optical
power_maxNomax steady-state power, W (peak/regenerative not counted)
prop_typeNopropulsion: electric | chemical | cold-gas | water; platforms: electric | chemical | any (the bus carries propulsion)
cycles_minNobattery: min cycle life
dish_min_mNoground station: min antenna diameter, m
gt_min_dbkNoground station: min G/T, dB/K
life_min_yNoany category: min design life in orbit, years
sunacc_maxNosun sensor: worst acceptable accuracy, deg
torque_minNowheels: min torque, mN*m
tvac_min_mNotest-facilities: min usable inner size (diameter or smallest side) of the thermal-vacuum chamber, m
update_minNostar trackers: min update rate, Hz
fov_min_degNosun sensors / star trackers / cameras: min field of view, deg
mag_res_maxNomagnetometer: worst resolution, nT
pos_acc_maxNoGNSS: worst position accuracy, m
res_max_degNopointing: max angular resolution, deg
shock_max_gNoseparation: max release shock, g
slip_min_chNoSADM: min slip-ring channels
storage_minNoOBC: min storage, GB
txpow_min_wNoradio: min TX RF power, W
accuracy_maxNostar trackers: worst acceptable cross-boresight accuracy, arcsec
beam_max_degNoantenna: max beamwidth, deg
channels_minNoGNSS: min channels
eirp_min_dbwNoground station: min EIRP, dBW
gain_min_dbiNoantenna: min gain, dBi
meop_min_barNotank/valve: min operating pressure, bar
momentum_minNowheels: min angular momentum storage, N*m*s
outpow_min_wNoEPS: min total output power, W
payvol_min_lNoplatforms: min volume for the payload, litres
payvol_min_uNoplatforms: min volume for the payload, U
polarizationNoantenna: RHCP|LHCP|linear|circular
ptrans_min_wNoSADM: min power transfer, W
range_min_utNomagnetometer: min field range, uT
sun_excl_maxNostar trackers: max acceptable sun exclusion angle, deg
swath_min_kmNocamera: min swath width, km
volume_min_lNotank/valve: min volume, L
bias_max_deghNoIMU: worst bias instability, deg/h
constellationNoGNSS: required constellation GPS|Galileo|GLONASS|BeiDou
flight_provenNoany category: true = only products with stated flight heritage (missions flown, heritage text or TRL 9)
paymass_min_gNoplatforms / deployers / separation systems: payload or satellite mass that must fit, grams
price_max_eurNomax indicative price, EUR (few vendors publish it — expect group C)
range_min_degNopointing: min travel range, deg
rate_min_kbpsNoradio: min data rate, kbps
shaker_min_knNotest-facilities: min shaker force, kN
thrust_max_mnNopropulsion: max thrust, mN
thrust_min_mnNopropulsion: min thrust, mN
battery_min_whNoplatforms: min battery capacity, Wh
buspower_min_wNoplatforms: min orbit-average power generation, W
capacity_min_uNodeployer: min capacity, U (your satellite size)
dipole_min_am2Nomagnetorquer: min dipole moment, A*m2
impulse_min_nsNopropulsion: min total impulse, N*s
paypower_min_wNoplatforms: min orbit-average power available to the payload, W
preload_min_knNoseparation: min preload/holding force, kN
reltime_max_msNoseparation: max release time, ms
capacity_max_whNobatteries: max capacity, Wh
capacity_min_whNobattery: min capacity, Wh
exclude_companyNomanufacturer names to EXCLUDE, comma-separated (for "not from Sodern")
exclude_countryNocountries or a region to EXCLUDE — "China", "Russia, Belarus", "Asia" (for "not Chinese", "non-US")
specimen_min_kgNotest-facilities: mass of your test article the lab must take, kg
pointacc_max_degNoplatforms / pointing mechanisms / ground stations: worst acceptable pointing accuracy, deg (30 arcsec = 0.0083)
panel_power_min_wNosolar panel: min BOL output, W
conductance_min_wkNothermal strap: min conductance, W/K
gyro_range_min_dpsNoIMU: min gyro range, deg/s

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / exclude_company
      Added value: +{
      +  "description": "manufacturer names to EXCLUDE, comma-separated (for \"not from Sodern\")",
      +  "type": "string"
      +}
    • addedInput schema / properties / exclude_country
      Added value: +{
      +  "description": "countries or a region to EXCLUDE — \"China\", \"Russia, Belarus\", \"Asia\" (for \"not Chinese\", \"non-US\")",
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "reaction-wheels",
      -  "star-trackers",
      -  "obc-computers",
      -  "batteries",
      -  "radios",
      -  "solar-panels",
      -  "propulsion",
      -  "sun-sensors",
      -  "magnetometers",
      -  "magnetorquers",
      -  "imus-gyros",
      -  "gnss-receivers",
      -  "eps",
      -  "deployers",
      -  "thermal",
      -  "antennas",
      -  "sdr-modems",
      -  "cameras",
      -  "structures",
      -  "platforms",
      -  "ground-stations",
      -  "sadm",
      -  "tanks-valves",
      -  "separation-systems",
      -  "pointing-mechanisms"
      -]New value: +[
      +  "reaction-wheels",
      +  "star-trackers",
      +  "obc-computers",
      +  "batteries",
      +  "radios",
      +  "solar-panels",
      +  "propulsion",
      +  "sun-sensors",
      +  "magnetometers",
      +  "magnetorquers",
      +  "imus-gyros",
      +  "gnss-receivers",
      +  "eps",
      +  "deployers",
      +  "thermal",
      +  "antennas",
      +  "sdr-modems",
      +  "cameras",
      +  "structures",
      +  "platforms",
      +  "ground-stations",
      +  "sadm",
      +  "tanks-valves",
      +  "separation-systems",
      +  "pointing-mechanisms",
      +  "test-facilities"
      +]
    • addedInput schema / properties / emc_min_m
      Added value: +{
      +  "description": "test-facilities: min test-article size the EMC / anechoic chamber takes, m",
      +  "type": "number"
      +}
    • addedInput schema / properties / shaker_min_kn
      Added value: +{
      +  "description": "test-facilities: min shaker force, kN",
      +  "type": "number"
      +}
    • addedInput schema / properties / specimen_min_kg
      Added value: +{
      +  "description": "test-facilities: mass of your test article the lab must take, kg",
      +  "type": "number"
      +}
    • addedInput schema / properties / test
      Added value: +{
      +  "description": "test-facilities: kinds of test the lab must ALL offer, comma-separated — vibration, shock, thermal-vacuum, thermal, emc, radiation, acoustic, magnetic, rf-antenna, mass-properties, outgassing, optical",
      +  "type": "string"
      +}
    • addedInput schema / properties / tvac_min_m
      Added value: +{
      +  "description": "test-facilities: min usable inner size (diameter or smallest side) of the thermal-vacuum chamber, m",
      +  "type": "number"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / flight_proven
      Added value: +{
      +  "description": "any category: true = only products with stated flight heritage (missions flown, heritage text or TRL 9)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / group
      Added value: +{
      +  "description": "page through one group only — use with offset from paging.next",
      +  "enum": [
      +    "A",
      +    "B",
      +    "C"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "items of groups B and C to return (default 10, max 50); group A comes in full up to 25",
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "start position inside the group (paging.next.offset of the previous answer)",
      +  "type": "integer"
      +}
  4. Changed3 schema fields changed
    • addedInput schema / properties / link_band
      Added value: +{
      +  "description": "platforms: radio band of the bus — UHF | VHF | L | S | X | Ku | Ka | optical",
      +  "type": "string"
      +}
    • addedInput schema / properties / orbit
      Added value: +{
      +  "description": "platforms: orbit the bus is designed for — LEO | SSO | VLEO | MEO | GEO | HEO | lunar | deep space (LEO, SSO and VLEO pass each other)",
      +  "type": "string"
      +}
    • changedInput schema / properties / prop_type / description
      Previous value: -"propulsion: electric | chemical | cold-gas | water"New value: +"propulsion: electric | chemical | cold-gas | water; platforms: electric | chemical | any (the bus carries propulsion)"
  5. Changed11 schema fields changed
    • addedInput schema / properties / battery_min_wh
      Added value: +{
      +  "description": "platforms: min battery capacity, Wh",
      +  "type": "number"
      +}
    • addedInput schema / properties / buspower_min_w
      Added value: +{
      +  "description": "platforms: min orbit-average power generation, W",
      +  "type": "number"
      +}
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "reaction-wheels",
      -  "star-trackers",
      -  "obc-computers",
      -  "batteries",
      -  "radios",
      -  "solar-panels",
      -  "propulsion",
      -  "sun-sensors",
      -  "magnetometers",
      -  "magnetorquers",
      -  "imus-gyros",
      -  "gnss-receivers",
      -  "eps",
      -  "deployers",
      -  "thermal",
      -  "antennas",
      -  "sdr-modems",
      -  "cameras",
      -  "structures",
      -  "ground-stations",
      -  "sadm",
      -  "tanks-valves",
      -  "separation-systems",
      -  "pointing-mechanisms"
      -]New value: +[
      +  "reaction-wheels",
      +  "star-trackers",
      +  "obc-computers",
      +  "batteries",
      +  "radios",
      +  "solar-panels",
      +  "propulsion",
      +  "sun-sensors",
      +  "magnetometers",
      +  "magnetorquers",
      +  "imus-gyros",
      +  "gnss-receivers",
      +  "eps",
      +  "deployers",
      +  "thermal",
      +  "antennas",
      +  "sdr-modems",
      +  "cameras",
      +  "structures",
      +  "platforms",
      +  "ground-stations",
      +  "sadm",
      +  "tanks-valves",
      +  "separation-systems",
      +  "pointing-mechanisms"
      +]
    • addedInput schema / properties / dv_min_ms
      Added value: +{
      +  "description": "platforms / propulsion: min delta-v, m/s",
      +  "type": "number"
      +}
    • changedInput schema / properties / form_u / description
      Previous value: -"structure: CubeSat form factor, U"New value: +"structures / platforms: CubeSat size, U (exact match)"
    • addedInput schema / properties / life_min_y
      Added value: +{
      +  "description": "any category: min design life in orbit, years",
      +  "type": "number"
      +}
    • changedInput schema / properties / paymass_min_g / description
      Previous value: -"deployer: min payload mass capability, g"New value: +"platforms / deployers / separation systems: payload or satellite mass that must fit, grams"
    • addedInput schema / properties / paypower_min_w
      Added value: +{
      +  "description": "platforms: min orbit-average power available to the payload, W",
      +  "type": "number"
      +}
    • addedInput schema / properties / payvol_min_l
      Added value: +{
      +  "description": "platforms: min volume for the payload, litres",
      +  "type": "number"
      +}
    • addedInput schema / properties / payvol_min_u
      Added value: +{
      +  "description": "platforms: min volume for the payload, U",
      +  "type": "number"
      +}
    • addedInput schema / properties / pointacc_max_deg
      Added value: +{
      +  "description": "platforms / pointing mechanisms / ground stations: worst acceptable pointing accuracy, deg (30 arcsec = 0.0083)",
      +  "type": "number"
      +}
  6. Changed4 schema fields changed
    • addedInput schema / properties / capacity_max_wh
      Added value: +{
      +  "description": "batteries: max capacity, Wh",
      +  "type": "number"
      +}
    • addedInput schema / properties / fov_min_deg
      Added value: +{
      +  "description": "sun sensors / star trackers / cameras: min field of view, deg",
      +  "type": "number"
      +}
    • addedInput schema / properties / mass_min
      Added value: +{
      +  "description": "min unit mass, grams (rare: \"heavier than\")",
      +  "type": "number"
      +}
    • addedInput schema / properties / thrust_max_mn
      Added value: +{
      +  "description": "propulsion: max thrust, mN",
      +  "type": "number"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"which component class to search (default reaction-wheels)"New value: +"which component class to search — ONE per call; for several classes call once per class (default reaction-wheels)"
  8. Changed2 schema fields changed
    • addedInput schema / properties / export
      Added value: +{
      +  "description": "required export status: ITAR-free | EAR99 | ITAR",
      +  "type": "string"
      +}
    • addedInput schema / properties / price_max_eur
      Added value: +{
      +  "description": "max indicative price, EUR (few vendors publish it — expect group C)",
      +  "type": "number"
      +}
  9. First observed

TDQS

A4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the read-only/idempotent annotations: exact A/B/C group semantics, limits on returned items, paging via group and offset, datasheet page citations, and the note that group C lists the most often unpublished fields. It also communicates the compact response shape and how truncation behaves.

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

Conciseness4/5

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

The description is dense and front-loaded with the main search concept, then covers output semantics and paging efficiently. The full category list is somewhat redundant with the schema enum, but it aids quick scanning and includes useful context for test-facilities.

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 a 90-parameter tool with no output schema, the description is remarkably complete: it defines grouping, truncation rules, paging via group and offset, counts, missing-data reporting, and verdict citations. An agent has enough context to call the tool and interpret its response.

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 coverage is 100% across 90 parameters, so the schema already defines each parameter. The description adds general guidance like 'Omit parameters you do not care about' and clarifies one category's special meaning (test-facilities items are companies), but it does not add per-parameter meaning beyond the schema.

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

Purpose4/5

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

The description gives a specific verb and resource: 'Reverse search over a typed spec layer' that returns items grouped as A, B, or C. This makes the tool's core function clearly recognizable. It does not explicitly name sibling tools to differentiate itself, though the A/B/C grouping and category list make the purpose fairly distinctive.

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

Usage Guidelines3/5

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

Usage is implied rather than explicit: 'pass a category and engineering requirements' and 'Omit parameters you do not care about' indicate when to use the tool. However, it does not state when not to use it or point to an alternative tool such as selection_guide or find_alternatives, so an agent must infer the decision boundary.

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.