Skip to main content
Glama

PartsTable

by com.partstable
OverviewDiscussionsAdmin

search-parts

Look up a batch of part numbers (max 25) against the PartsTable catalog. Returns per-part identity summary and whether each exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partNumbersYesPart numbers to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / condition
      Removed value: -{
-  "default": "any",
-  "description": "Filter by item condition",
-  "enum": [
-    "NEW",
-    "USED",
-    "REFURBISHED",
-    "any"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "default": 10,
-  "description": "Max results to return (1-50)",
-  "maximum": 50,
-  "minimum": 1,
-  "type": "number"
-}
    • removedInput schema / properties / manufacturer
      Removed value: -{
-  "default": "auto",
-  "description": "Manufacturer hint for better results",
-  "enum": [
-    "HPE",
-    "Dell",
-    "IBM",
-    "Lenovo",
-    "auto"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / partNumber
      Removed value: -{
-  "description": "IT hardware part number to search for",
-  "type": "string"
-}
    • addedInput schema / properties / partNumbers
      Added value: +{
+  "description": "Part numbers to look up",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 25,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "partNumber"
-]New value: +[
+  "partNumbers"
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly indicates a read-only lookup operation by stating 'Look up' and describing the return. However, it lacks disclosure of potential error handling, partial results, or any authorization requirements. The description is honest but could add more behavioral context.

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?

The description consists of two concise sentences with no wasted words. It front-loads the core action 'Look up a batch of part numbers' and immediately adds the batch limit and output summary. Every sentence is informative.

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?

Given the tool's low complexity (one required parameter, no output schema, no annotations), the description covers the essential purpose, input, batch limit, and output nature. It does not address error behavior or response format, but for a straightforward search tool, it is reasonably complete.

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 description coverage is 100% since the only parameter 'partNumbers' has a description. The tool description adds value beyond the schema by explaining that it processes a batch, sets the maximum size, and describes the output (per-part summary and existence). This goes beyond the baseline of 3 for high coverage.

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?

The description clearly states the verb 'Look up a batch of part numbers', the resource 'PartsTable catalog', and the output 'per-part identity summary and whether each exists'. It also specifies the batch size limit of 25, which distinguishes it from sibling 'get-part' (likely single-part lookup).

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?

The description implies use for batch part number lookup and mentions the size limit, but does not explicitly state when to use this tool vs. siblings like 'get-part' for single parts or 'validate-pn' for validation. No alternatives or exclusions are given.

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

All PartsTable toolsInspect
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