Skip to main content
Glama

Search FPV parts

search_parts
Read-only

Finds published parts of one type by spec. filters maps a spec field to a number (equals, or any element of a list), a string (case-insensitive substring) or {min, max} (numeric range). query matches brand and model. An unknown field returns the type's field list. Example: type=motor, filters={"stator": "2207", "weight_g": {"max": 33}}.

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": {
      "type": "<type>"
    },
    "name": "search_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesPart type to search
limitNoMost results to return
queryNoWords that must appear in brand + model
filtersNoSpec field -> number, list, substring or {min, max}, e.g. {"stator": "2207"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / filters / description
      Added value: +"Spec field -> number, list, substring or {min, max}, e.g. {\"stator\": \"2207\"}"
    • addedInput schema / properties / limit / description
      Added value: +"Most results to return"
    • addedInput schema / properties / type / description
      Added value: +"Part type to search"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds real behavior beyond them: only published parts are returned, and an unknown filter field returns that type's field list as a discovery path. Remaining gaps, such as result ordering and total-count/pagination behavior, are modest against the annotation coverage.

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 tight sentences with the core purpose first, then filter semantics, then query semantics, then a worked example that is directly reusable. Nothing is repeated from the schema and no sentence is filler.

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?

For a four-parameter search with a free-form nested filters object and no output schema, the description covers the risky parts: filter value interpretation and the unknown-field discovery path. It stops short of describing the shape of a returned part record, which leaves some uncertainty about what fields can then be read.

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 already 100%, so the baseline is 3, but the description goes further by disambiguating filter value semantics: a number means equality or any element of a list, a string is a case-insensitive substring, and {min, max} is a numeric range. The only undocumented nuance is whether limit truncates silently.

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?

Opens with a specific verb and resource plus a scope qualifier: 'Finds published parts of one type by spec'. The 'by spec' framing and the 'published' qualifier distinguish it from part_specs and the other fw_* siblings, so an agent can pick it without opening a schema.

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 conveyed only by an inline example (type=motor with two filters) and a fallback hint that an unknown field returns the type's field list. There is no explicit statement of when to prefer this over part_specs for discovering fields, nor any when-not guidance, so selection logic must be inferred.

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.