Skip to main content
Glama
Sign In

materials

by com.spacemushroom
OverviewDiscussionsAdmin

List the parts of a product

product_parts
Read-onlyIdempotent

The flat parts list of one product in source order: assembly, part, function, material (and material id), form, finish, standard, part number, supplier, part specs, quote and source. Use it when you need the parts and not the whole record, for example "the thermal control parts of Parker Solar Probe" (part_function thermal control) or "which parts of Falcon 9 are aluminium" (material). Accepts an id, title or alias. An empty list means no such parts were published in the sources read.

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": {
      "product": "<product>"
    },
    "name": "product_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct id, title or alias
materialNoOnly parts of this material id, for example aluminium-2219
part_functionNoPart function: structure, thermal control, power, propulsion, mechanisms, avionics, optics, protection or other. DERIVED by explicit name rules from the part names (marked function_basis "derived"), not stated by the sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds non-obvious behavior the annotations cannot: results come back in source order, and an empty list means no such parts were published in the sources read, which prevents an agent mistaking an empty result for an error.

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?

Three compact sentences, front-loaded with what is returned before the usage condition and the empty-result caveat. The field enumeration is long but earns its place because there is no output schema to describe the shape.

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 compensates by listing every returned field, and with three parameters at full schema coverage the inputs need no further explanation. Behavior on empty results and accepted identifier forms are both stated, leaving nothing an agent needs in order to call it correctly.

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 description coverage is 100%, so the parameters are already documented and the baseline is 3. The description adds value by clarifying that 'product' accepts an id, title or alias, and by giving worked examples of the material ('which parts of Falcon 9 are aluminium') and part_function ('the thermal control parts of Parker Solar Probe') filters.

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 names a specific verb and resource ('the flat parts list of one product in source order') and enumerates exactly what is returned (assembly, part, function, material, form, finish, standard, part number, supplier, specs, quote, source). This distinguishes it from the whole-record sibling get_product by stating it gives 'the parts and not the whole record'.

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 gives a clear usage condition ('use it when you need the parts and not the whole record') and backs it with two concrete scenarios that map to the part_function and material filters. It stops short of naming the alternative tool explicitly, so the routing is implied rather than spelled out.

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

All materials toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources