Skip to main content
Glama

Hardware you can design around

list_available_hardware
Read-onlyIdempotent

Parts (magnets, inserts, bearings and more) that Printlooper print shops stock and have confirmed exact dimensions for, ready to build a design around on Printlooper. Filter by words in the part name.

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": "list_available_hardware"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFor example "magnet" or "M3 insert"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful behavioral context — that these parts are shop-stocked and have confirmed exact dimensions, i.e. dimensionally trustworthy — but says nothing about pagination, default result counts, or result ordering.

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?

A single compact sentence that front-loads the resource definition and closes with the filtering hint. No filler, though the phrase 'ready to build a design around on Printlooper' repeats the Printlooper branding already implied by 'Printlooper print shops' and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter, no-required-args read tool with no output schema, the description covers what the resource is and how to filter it. It falls short on result-volume behavior (the limit parameter and its default/cap) and on differentiating the tool from its close sibling, both of which an agent needs to call it correctly.

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%: 'query' is documented in the schema with examples, and the description reinforces that matching is on words in the part name, which is a slight addition over the schema's example. The 'limit' parameter has no description in either place, so default 20 / max 50 behavior and what limit actually controls is left undocumented.

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 names a specific resource — hardware parts (magnets, inserts, bearings) stocked by Printlooper print shops with confirmed exact dimensions — and implies a listing operation. It is clear what an agent gets back, though the verb 'list' is never stated outright and no sibling is named to sharpen the boundary against list_my_hardware.

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?

The single sentence 'Filter by words in the part name' gives an implied usage pattern for the query parameter, but there is no explicit when-to-use/when-not-to-use guidance. In particular, nothing distinguishes this catalog-wide listing from the sibling list_my_hardware, leaving the agent to infer the difference from the name alone.

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.

Resources