Skip to main content
Glama

Feature Library

Find parts for a job

find_parts
Read-only

Free. Ranks the library’s parts for a job described in words, with why each fits and what it costs on the target platform (median ms a frame at 1920×1080 on a measured machine and tier). Strong matches for the job come first (each part says match: strong or loose), then looser ones; within each, parts that fit the platform and budget lead, then those over the budget (overBudget), then those that need WebGPU on a platform without it (blocked). For an interface job, 3D, simulation and effects parts rank lower. Each part says what it runs in (runsIn): raw WebGPU passes, a three.js scene, a 2D canvas or the DOM; a three.js part needs a three.js app, so check it against your renderer before installing. When the words name a look or ask for one, the matching looks come back too. Search by the job, not by a name.

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": {
      "job": "<job>"
    },
    "name": "find_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesWhat the part has to do, e.g. "date range filter for a dashboard" or "grass that bends round a walker".
kitNoOptional: a kit id (e.g. dashboard) to search only its parts and those of the kits it is built on.
limitNoAt most this many parts (default 10).
budgetNoMs a frame the part may cost on that platform (the worse of GPU and CPU).
platformNoThe target: desktop (the reference laptop, the default), laptop (integrated GPU), phone, a machine id from a part’s costs, or "no-webgpu" for browsers without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the readOnly/openWorld annotations: it discloses the ranking order (strong matches, then loose; fit+budget, then overBudget, then blocked), the interface-job demotion rule, the presence of match/runsIn/overBudget fields, and the renderer compatibility caveat before installing. These are behavioral traits an agent could not obtain from the structured fields.

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?

Front-loaded with the core action and the critical "search by the job, not by a name" rule; the ranking tiers are laid out in logical order. It is dense and runs long in places, with the runsIn/three.js sentence doing double duty, but nearly every clause carries decision-relevant 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?

There is no output schema, so the description must carry return-value meaning, and it does: match strength, cost in median ms/frame, overBudget, blocked, runsIn renderer targets, and returned looks. For a 5-parameter read tool this covers everything an agent needs to call it correctly and interpret results.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema for how budget and platform shape results (budget ordering via overBudget, WebGPU blocking on no-webgpu platforms, 1920×1080 measured-machine costs) and clarifies that job is a description of intent. The line about checking runsIn against your renderer adds practical semantics the schema does not.

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?

States a specific verb+resource+scope: "Ranks the library's parts for a job described in words." That clearly distinguishes it from siblings that fetch a single part (get_part), install, or check, and it immediately tells the agent the input is a natural-language job description rather than a name.

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?

Gives an explicit query-formulation rule ("Search by the job, not by a name") and notes it is free, which is real routing guidance. It does not explicitly name which sibling to use when you already know the part id or want to install/verify, so the alternative-to-this-tool mapping 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources