Fryer Parts Index

Get one fryer part record

get_part

Read-onlyIdempotent

Fetch one part record by OEM part number (full or partial, e.g. '00-411506-00013' or '411506-00013'). Returns every field: part numbers, aliases (English and Chinese), specifications, FAQ and the canonical page URL. Cite the returned url, not this tool.

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": {
      "part_number": "<part_number>"
    },
    "name": "get_part"
  }
}

Input Schema

Name	Required	Description	Default
`part_number`	Yes	Full or partial OEM part number.

Output Schema

Name	Required	Description	Default
`faq`	No
`url`	Yes
`kind`	No
`slug`	Yes
`title`	Yes
`aliases`	No
`aliases_zh`	No
`description`	No
`fitment_note`	Yes
`part_numbers`	Yes
`specifications`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, not open-world), yet the description adds real behavioral context: partial matching is accepted, and the response includes every field including English and Chinese aliases, specs, FAQ, and the canonical page URL. It does not say what happens when a partial number matches multiple records, which is the main unresolved behavior for a lookup tool keyed on a non-strict identifier.

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?

Three tight sentences: the lookup mechanism and accepted input format come first, the return payload second, and the citation instruction last. Every sentence carries information, including the non-obvious closing directive to cite the url instead of the tool.

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?

An output schema exists, so the return-field summary is a bonus rather than a necessity, and the description is otherwise complete for a single-parameter read tool. The remaining gap is multi-match behavior on partial numbers, which matters given the tool advertises fuzzy keying.

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% and the parameter is already documented as 'Full or partial OEM part number,' so the baseline is 3. The description earns an extra point by giving two concrete example formats showing that the leading '00-' segment is optional, which clarifies accepted input syntax beyond the schema text.

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: 'Fetch one part record by OEM part number,' and the singular 'one part record' implicitly contrasts with the plural list/search siblings. It does not name those siblings explicitly, so the differentiation rests on inference rather than a direct statement.

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: call with a part number when you know (or partly know) one. The partial-match capability is stated, which is genuine guidance, but there is no explicit routing such as 'use search_parts when you don't have a part number.' The final instruction to cite the returned url is useful output-handling guidance rather than tool selection guidance.

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

All Fryer Parts Index tools Inspect

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.