Laptop Part Finder

Get a repair guide

get_repair_guide

Read-only

Read one repair guide's full steps once you have its slug; use search_repair_guides to find slugs by model, component or words. Returns Markdown steps with manual page citations, the official manual URL, the service classification and scope restrictions, typically 2 to 17 KB. The slug must match exactly (case and surrounding spaces ignored); an unknown slug is an error result: No guide "". Use search_repair_guides. Not bench-tested: follow the scope restrictions and the OEM manual. Read-only.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Required. Guide slug from search_repair_guides, e.g. "hp-elitebook-840-g6-battery-replacement".

Output Schema

Name	Required	Description
`url`	No
`slug`	Yes
`model`	No
`pages`	No
`title`	Yes
`api_url`	No
`license`	No
`markdown`	Yes
`component`	No
`terms_url`	No
`fit_status`	No	Present when there is no fit or no result: LPF has no OEM document for it. Never means incompatible.
`model_name`	No
`source_url`	No
`attribution`	No
`absence_note`	No
`bench_tested`	No
`manufacturer`	No
`source_title`	No
`data_revision`	No
`service_classification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / slug / description

Previous value: -"e.g. hp-elitebook-840-g6-battery-replacement"New value: +"Required. Guide slug from search_repair_guides, e.g. \"hp-elitebook-840-g6-battery-replacement\"."

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "absence_note": {
+      "type": "string"
+    },
+    "api_url": {
+      "type": "string"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "bench_tested": {
+      "type": "boolean"
+    },
+    "component": {
+      "type": "string"
+    },
+    "data_revision": {
+      "type": "string"
+    },
+    "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"
+    },
+    "license": {
+      "type": "string"
+    },
+    "manufacturer": {
+      "type": "string"
+    },
+    "markdown": {
+      "type": "string"
+    },
+    "model": {
+      "type": "string"
+    },
+    "model_name": {
+      "type": "string"
+    },
+    "pages": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "service_classification": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    },
+    "source_title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "terms_url": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "title",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedOct 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, yet the description still adds substantial behavioral detail: Markdown steps with manual page citations, official manual URL, service classification, scope restrictions, and 2-17 KB payload size. It also warns the content is "Not bench-tested" and that scope restrictions/OEM manual must be followed, which the annotations cannot convey. Minor deduction only because "Read-only" merely restates the annotation and the slug-matching rule is repeated in the next section.

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 purpose and the slug prerequisite, and dense with useful facts. It loses a point for redundancy: "use search_repair_guides" appears twice, and "Read-only" repeats the annotation.

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?

For a single-parameter lookup tool with an output schema, this covers everything an agent needs: where to get the slug, exact-match rules, error behavior, and what the returned content contains and how large it is. No gap remains that would cause a misinvocation.

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 slug parameter is already documented with an example, so the baseline is 3. The description goes beyond that by specifying exact-match semantics (case and surrounding spaces ignored) and the literal error shape `No guide "<slug>"`, which the schema does not state.

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 and resource ("Read one repair guide's full steps") plus the precondition ("once you have its slug") and names the sibling it is not (search_repair_guides). An agent can distinguish this fetch-by-key tool from the search sibling without consulting either schema.

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: use search_repair_guides to find slugs by model, component or words, then call this with the slug. It also states the failure condition for an unknown slug, so the agent knows the calling contract and how to recover.

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?