Laptop Part Finder

Get models a part fits

get_part_fits

Read-only

Use when you hold one exact part number and want every model it is documented to fit. Yes/no for specific models, or several part numbers at once: check_part_fits. Full part record: get_part. Model to parts: get_model_parts. Keyword text: search_parts. Part numbers match as in get_part (case, dashes, spaces, leading zeros, retired numbers); several matches return status ambiguous, so ask which is printed on the part. Not found is an error result; a part with no documented models returns fits [] and fit_status no_documented_fit. Neither means incompatible. Screen fits include panel_options. Read-only.

Input Schema

Name	Required	Description	Default
`client`	No	Optional: your agent or app name (letters and digits), used only for anonymous usage counts.
`part_number`	Yes	Required. OEM part number, with or without dashes or spaces, e.g. "01FR025", "7K4PW", "L78555-005".

Output Schema

Name	Required	Description
`url`	No
`fits`	No
`name`	No
`note`	No
`type`	No
`brand`	No
`match`	No
`query`	No
`specs`	No
`status`	No
`api_url`	No
`license`	No
`lpf_url`	No
`message`	No
`buy_links`	No
`terms_url`	No
`candidates`	No
`fit_status`	No	Present when there is no fit or no result: LPF has no OEM document for it. Never means incompatible.
`source_url`	No
`superseded`	No
`attribution`	No
`description`	No
`part_number`	No
`absence_note`	No
`display_name`	No	Short human label; not an identifier
`data_revision`	No
`verified_date`	No
`normalized_from`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / part_number / description

Previous value: -"Required. OEM part number, with or without dashes or spaces, e.g. \"01FR025\" or \"7K4PW\""New value: +"Required. OEM part number, with or without dashes or spaces, e.g. \"01FR025\", \"7K4PW\", \"L78555-005\"."

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / part_number / description

Previous value: -"Required. OEM part number, with or without dashes or spaces, e.g. \"L18M3PF1\" or \"01AV489\""New value: +"Required. OEM part number, with or without dashes or spaces, e.g. \"01FR025\" or \"7K4PW\""

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / part_number / description

Added value: +"Required. OEM part number, with or without dashes or spaces, e.g. \"L18M3PF1\" or \"01AV489\""

Changed4 schema fields changedNov 1, 2026
- addedOutput schema / properties / fits / items / properties / checked_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / fits / items / properties / source_document_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / fits / items / properties / source_title
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / fits / items / properties / verification_level
```
Added value: +{
+  "enum": [
+    "manufacturer_document",
+    "reseller_listing",
+    "unknown"
+  ],
+  "type": "string"
+}
```

Changed1 schema field changedNov 1, 2026

addedOutput schema / properties / display_name

Added value: +{
+  "description": "Short human label; not an identifier",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "part_number",
+        "fits"
+      ]
+    },
+    {
+      "required": [
+        "status",
+        "candidates"
+      ]
+    }
+  ],
+  "properties": {
+    "absence_note": {
+      "type": "string"
+    },
+    "api_url": {
+      "type": "string"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "brand": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "buy_links": {
+      "items": {
+        "properties": {
+          "affiliate": {
+            "type": "boolean"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "merchant": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "candidates": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "data_revision": {
+      "type": "string"
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fit_status": {
+      "description": "Present when there is no fit or no result: LPF has no OEM document for it. Never means incompatible.",
+      "enum": [
+        "no_documented_fit"
+      ],
+      "type": "string"
+    },
+    "fits": {
+      "items": {
+        "properties": {
+          "confidence": {
+            "enum": [
+              "oem_manual",
+              "retailer",
+              "unverified"
+            ],
+            "type": "string"
+          },
+          "confidence_note": {
+            "type": "string"
+          },
+          "constraints": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "model": {
+            "type": "string"
+          },
+          "model_name": {
+            "type": "string"
+          },
+          "notes": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "panel_options": {
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "source_detail": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          },
+          "verification_basis": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "verified_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "model",
+          "source_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "license": {
+      "type": "string"
+    },
+    "lpf_url": {
+      "type": "string"
+    },
+    "match": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "normalized_from": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "part_number": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "specs": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "status": {
+      "enum": [
+        "ambiguous"
+      ],
+      "type": "string"
+    },
+    "superseded": {
+      "type": "object"
+    },
+    "terms_url": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "verified_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / client / description

Previous value: -"Optional: your agent or app name (letters and digits), used only to attribute outbound affiliate links."New value: +"Optional: your agent or app name (letters and digits), used only for anonymous usage counts."

First observedOct 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare read-only and closed-world; the description adds the matching normalization rules (case, dashes, spaces, leading zeros, retired numbers), the 'ambiguous' status on multiple matches, the distinction between a not-found error and an empty fits result with fit_status no_documented_fit, and the panel_options field on screen fits. It also warns that neither outcome means incompatible.

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 when-to-use clause and no filler, but the telegraphic fragments ('Yes/no for specific models, or several part numbers at once: check_part_fits') read as terse shorthand and take a re-read to parse.

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?

Even though an output schema exists, it still clarifies the two easily-confused outcomes (error vs empty fits) and the panel_options field, so an agent can interpret results without guessing. Nothing needed to call it correctly is missing.

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 baseline is 3, but the description adds matching semantics the schema does not convey: leading zeros, retired numbers, and the consequence of multiple matches. The client parameter is only covered by the schema, which is fine.

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, resource and scope: 'Use when you hold one exact part number and want every model it is documented to fit.' That is immediately distinguishable from the sibling tools it goes on to name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: check_part_fits for yes/no or batch checks, get_part for the full record, get_model_parts for the reverse direction, search_parts for keyword text. It also tells the agent to ask which number is printed on the part when the match is ambiguous.

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

All Laptop Part Finder 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.

Resources

Need Help?