easyeda-mcp-pro

Get BOM sourcing info

easyeda_bom_sourcing

Read-onlyIdempotent

Retrieves pricing and availability for all BOM parts from specified suppliers, enabling component sourcing and cost estimation for your project.

Instructions

Retrieve pricing and availability information for all parts in the project BOM from specified suppliers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes
`suppliers`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`parts`	Yes
`project_id`	Yes
`total_parts`	Yes
`not_available`	No
`keyless_sourcing_enabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.2Oct 2, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed6 schema fields changedv0.19.1Jul 15, 2026
- addedOutput schema / properties / keyless_sourcing_enabled
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / parts / items / properties / sourcing / items / properties / cache_age_seconds
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / parts / items / properties / sourcing / items / properties / classification
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / parts / items / properties / sourcing / items / properties / from_cache
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / parts / items / properties / sourcing / items / properties / tier
```
Added value: +{
+  "enum": [
+    "keyless",
+    "authenticated"
+  ],
+  "type": "string"
+}
```
- changedOutput schema / properties / parts / items / properties / sourcing / items / required
```
Previous value: -[
-  "supplier",
-  "in_stock"
-]New value: +[
+  "supplier",
+  "tier",
+  "in_stock"
+]
```
First observedv0.19.0Jul 4, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds almost no behavioral context beyond that: it does not say what happens if 'suppliers' is omitted (all suppliers? default set?), whether it hits an external network/API, or how stale the pricing data may be. The phrase 'from specified suppliers' is the only added detail.

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized, though it is perhaps too terse given the parameter ambiguity it leaves unresolved.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value structure need not be described. Still, for a tool with 0% schema parameter coverage, the description omits the supplier-value format and default behavior, which are needed to invoke it correctly. Adequate but with a clear gap.

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%, so the description carries the full burden for both parameters. It implies projectId (the BOM project) and suppliers, but gives no guidance on supplier identifier format (names? IDs? enum values?) or whether the suppliers list is optional with a default. This leaves genuine ambiguity for the caller.

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 ('Retrieve') and resource ('pricing and availability information for all parts in the project BOM'), which is clearly distinguishable from siblings like easyeda_bom_validate, easyeda_bom_export, and easyeda_bom_quality_report. However, it never explicitly names or contrasts itself with those siblings, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description says nothing about when to use this tool versus the other BOM tools (validate, export, generate, quality_report), nor any prerequisites such as whether the BOM must already exist. Usage must be inferred entirely from the name and purpose sentence.

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

Deploy Server