SkoIA Parts

Search physical parts

search_parts

Read-onlyIdempotent

Searches the verified local product and part-type index without inventing identities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`tool`	Yes
`facts`	Yes
`status`	Yes
`warnings`	Yes
`requestId`	Yes
`confidence`	Yes
`provenance`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 2, 2026
- addedOutput schema / properties / confidence / properties / score / anyOf
```
Added value: +[
+  {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / confidence / properties / score / maximum
```
Removed value: -1
```
- removedOutput schema / properties / confidence / properties / score / minimum
```
Removed value: -0
```
- removedOutput schema / properties / confidence / properties / score / type
```
Removed value: -"number"
```
First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already communicate read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context by emphasizing that the index is 'verified' and local, and that the tool will not fabricate identities. This goes beyond the structured annotations without contradicting them.

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?

A single sentence that is tightly worded and front-loaded with the core action. Every phrase contributes meaning: 'verified', 'local', 'product and part-type index', and 'without inventing identities' all add useful semantic weight.

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 simple two-parameter schema, rich annotations, and presence of an output schema, the description is largely sufficient. The main missing piece is explicit routing guidance relative to sibling search or generation tools, but this is a minor gap for such a straightforward search operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no parameter-specific meaning for 'query' or 'limit'. It does clarify what the query searches against, but it does not explain accepted formats, matching behavior, or how limit affects results. The description fails to compensate for the completely undocumented parameters.

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 uses a specific verb ('Searches') and identifies a clear resource ('verified local product and part-type index'). 'Without inventing identities' communicates a hard constraint and helps distinguish this tool from generation-oriented siblings like generate_artifact or synthesize_physical_solution.

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 when to use the tool: when searching a trusted, local, verified index rather than inventing or generating possibilities. However, it does not explicitly name alternatives or state when not to use this tool, so usage guidance remains implicit rather than direct.

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

All SkoIA Parts 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?