Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

submit_component_rfq

Submit an electronic component RFQ for human sourcing in Shenzhen, China. Use for hard-to-find, obsolete, EOL, spot-market, BOM, or other components requiring China sourcing. Maria Jurk reviews the request. This tool does not claim real-time inventory or fabricate pricing or availability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "part_number": "<part_number>",
      "quantity": "<quantity>",
      "email": "<email>"
    },
    "name": "submit_component_rfq"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the buyer or contact person submitting the RFQ.
emailYesBuyer email address where Maria Jurk can respond to the RFQ.
notesNoAdditional sourcing requirements such as date code, target price, destination, lead time, packaging, acceptable alternatives, or BOM context.
companyNoBuyer company or organization name.
quantityYesRequired quantity, including units when useful, for example '500 pcs'.
part_numberYesExact manufacturer part number or component identifier the buyer needs sourced.
manufacturerNoComponent manufacturer or brand, if known. Leave empty when unknown.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the RFQ was accepted successfully.
errorNoError message when the RFQ could not be accepted.
statusNoRFQ processing status, such as rfq_received.
locationNoLocation of the human sourcing specialist.
referenceNoUnique Jurk RFQ reference for the submitted request.
handled_byNoHuman sourcing specialist responsible for reviewing the RFQ.
http_statusNoUpstream HTTP status when the RFQ could not be accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already state it is a non-read-only, non-idempotent, open-world write, and the description adds real context beyond that: a named human reviewer (Maria Jurk) performs the sourcing, so the operation is asynchronous and human-in-the-loop. The explicit disclaimer about not claiming real-time inventory or fabricating pricing/availability is valuable expectation-setting, though turnaround time and duplicate-submission behavior are not stated.

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?

Four short sentences, front-loaded with purpose then use cases, then reviewer, then an honesty disclaimer. There is no wasted wording, though the final disclaimer sentence is defensive framing rather than invocation-relevant detail.

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?

An output schema exists, so return values need not be explained, and the seven parameters are fully documented in the schema. What remains unstated is what happens after submission (response timeline, whether duplicate RFQs are merged), which matters for a human-review submission tool but is a modest gap.

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

Parameters3/5

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

With 100% schema description coverage across all seven parameters, the schema already carries full parameter meaning, including required vs optional and example formats like '500 pcs'. The description adds no per-parameter guidance beyond what the schema provides, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('Submit an electronic component RFQ') plus a scope ('human sourcing in Shenzhen, China') and enumerates qualifying cases (obsolete, EOL, spot-market, hard-to-find). It is clear what the tool does, but it does not distinguish itself from overlapping siblings such as submit_bom or request_huaqiangbei_search, even though 'BOM' is listed as a valid input case.

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 gives solid when-to-use criteria via the component categories, but offers no exclusions or named alternatives despite a crowd of related siblings (submit_bom, request_huaqiangbei_search, request_market_price_check, submit_supplier_check). The mention of 'BOM' actually invites confusion with submit_bom rather than resolving it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources