Skip to main content
Glama

Material Get

material_get
Read-only

Looks up a material by name and returns an FEM-card-compatible property card with modulus, density, strength, and cost values. On a miss it returns a failure reason with a suggested name.

Instructions

Look up a material by name (e.g. 'AL6061-T6'). Returns the full property card as SI quantity strings (YoungsModulus, PoissonRatio, Density, yield_strength, fracture_toughness, thermal_conductivity, cte, rough_cost, refractive_index where applicable, source, basis). The structural keys are FEM-card-compatible, so the result feeds fem_set_material directly. On a miss returns {ok:false, reason} with a did_you_mean suggestion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
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

A4.1/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, so the safety profile is covered; the description adds genuine behavioral detail beyond that — the SI-string return shape, the enumerated key set, and the exact miss behavior ({ok:false, reason} plus a did_you_mean suggestion). What it does not disclose is name-matching semantics (exact vs normalized/fuzzy) and whether workspace scoping changes the result, which matter for a lookup tool.

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?

Four compact sentences: purpose first, then return shape, then downstream compatibility, then failure mode. No filler, and the enumerated key list earns its space because there is no output schema to carry that information.

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?

With no output schema, the description carries the full burden of describing returns and does so by naming the exact keys and their representation (SI quantity strings), plus the structured miss response. Combined with annotations covering read-only/non-open-world, an agent has everything needed to call this correctly and interpret the result.

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 50%: 'workspace' is documented in the schema ('Run this call in this named workspace') while 'name' has no schema description at all. The description partially compensates by giving a concrete example value ('AL6061-T6'), which is the main thing an agent needs for the undocumented parameter, but it never explains workspace scoping or name-matching rules.

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 verb+resource ('Look up a material by name') with a concrete example ('AL6061-T6'), so an agent immediately knows this is a single-record name-keyed lookup rather than a listing or search. It never names the obvious siblings (material_list, material_select, catalog_nearest) to make the boundary explicit, which is the only thing keeping it from a 5.

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 gives a clear usage context: call it with a material name when you need a full property card, and the result is explicitly designed to feed fem_set_material directly, which tells the agent where this sits in the FEM workflow. It stops short of stating when NOT to use it (e.g. browsing, when the name is unknown — cases that clearly belong to material_list/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