Skip to main content
Glama

Material Select

material_select
Read-only

Filter materials by min/max property criteria, then rank surviving candidates by specific strength, stiffness, cost, or density to choose a material for design.

Instructions

Ashby-style selection: filter the corpus, then rank survivors.

criteria keys are min_/max_ (e.g. min_yield_mpa, max_density_g_cc, min_service_temp_c). rank_by: specific_strength | specific_stiffness | strength | stiffness | cost | density. Returns {rank_by, count, criteria, candidates:[{name, score, yield_mpa, density_g_cc, youngs_gpa, cost_usd_kg}, ...]} best-first; an empty filter returns no candidates rather than the closest miss.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "material_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
rank_byNospecific_strength
criteriaNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real behavior on top: result ordering is best-first, and a filter that matches nothing yields no candidates rather than a nearest-miss fallback. It does not state corpus size, units assumed for criteria values, or whether ranking is descending.

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?

Front-loaded with the core operation, then parameter syntax, then return shape — no filler sentences. The inline return-shape sketch earns its place since no output schema exists.

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?

With no output schema, describing the returned {rank_by, count, criteria, candidates:[...]} object is valuable and done well. Along with the criteria and rank_by semantics, an agent can call this correctly; only the material corpus scope and value units remain unstated.

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 only 33% (only workspace is documented), so the description must compensate — and it largely does: it gives the criteria key convention min_<accessor>/max_<accessor> with concrete examples and enumerates the rank_by options, which the schema leaves as an unconstrained string. It stops short of listing valid accessors beyond the examples.

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?

States a specific operation: filter the material corpus by criteria, then rank survivors — a clear verb+resource pair. It is distinguishable in spirit from material_get/material_list/catalog_search, though it never names those siblings explicitly to rule them in or out.

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 by the 'filter then rank' framing, and one exclusion-like behavior is given (an empty filter returns no candidates rather than the closest miss). However there is no explicit statement of when to choose this over material_list, material_get, or catalog_nearest.

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

Deploy Server

Other Tools