Skip to main content
Glama

FPV part spec sheet

part_specs
Read-only

The full spec sheet of one part by its slug (the last segment of its fpv-db.com URL, e.g. iflight-xing2-2207 for /motors/iflight-xing2-2207/): specs, bench thrust table where measured, VTX table where published, the sources the specs were verified against, and caveats.

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": {
      "slug": "<slug>"
    },
    "name": "part_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPart slug, e.g. iflight-xing2-2207 (from search_parts or the page URL)
typeNoPart type, if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Part slug, e.g. iflight-xing2-2207 (from search_parts or the page URL)"
  2. First observed

TDQS

A3.8/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 safety is covered. The description goes beyond them by describing the payload shape — measured bench thrust tables, VTX tables where published, verification sources, and caveats — which tells the agent how much and what kind of data to expect. It does not address behavior when the slug is invalid or the part lacks bench data.

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?

Single sentence with the core purpose front-loaded, followed by a return-value enumeration. The parenthetical URL example is somewhat long but earns its place for slug disambiguation; no filler or repetition.

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 describe return content — and it does so thoroughly for each data category, including conditional availability ('where measured', 'where published'). Combined with the high-coverage input schema, an agent has enough to call this 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 100%, so the baseline is 3. The description explains the slug precisely (the last URL segment, with a worked example), which is marginally more specific than the schema's 'from the page URL', but it says nothing about the optional `type` enum parameter or its effect on resolution.

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 and resource: the full spec sheet of one part identified by slug. It enumerates the returned content (specs, bench thrust table, VTX table, sources, caveats), which makes the tool's identity concrete. It does not explicitly name search_parts as the sibling to use for browsing/filtering, so sibling differentiation is only implied.

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 implied by 'one part by its slug' — the agent can infer this is for fetching details of a single known part rather than searching. There is no explicit when-not guidance, no mention of what to do if the slug is unknown, and no pointer to search_parts for discovering slugs.

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.