Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

submit_bom

Submit a multi-line electronic component BOM for human sourcing in Shenzhen. This creates one sourcing request for the complete BOM. It does not purchase parts, guarantee availability, or confirm pricing.

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": {
      "items": "<items>",
      "email": "<email>"
    },
    "name": "submit_bom"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailYes
itemsYes
notesNo
companyNo
confirm_submissionNo

Output Schema

NameRequiredDescriptionDefault
messageYes
acceptedYes
locationYes
referenceYes
handled_byYes
line_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and non-idempotent, and the description usefully reinforces this by saying it 'creates one sourcing request' — a repeat call would create a second request — and by disclaiming purchase, availability, and pricing guarantees, which sets accurate expectations for a human-in-the-loop workflow. It does not mention where the submitted email goes or how the requesting party is contacted, leaving a modest gap.

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?

Three short sentences with zero waste: action and scope first, side effect second, exclusions third. Nothing is redundant or buried.

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?

The output schema and annotations cover return values and the safety profile, and the description handles the 'what happens next' question well. For a six-parameter, non-idempotent submission tool with an undocumented confirmation flag and no sibling routing guidance, however, the definition leaves gaps an agent must guess at.

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% across six parameters, so the description carries the burden and largely fails: 'items' is only implied by 'multi-line BOM', and required 'email' is unexplained (presumably a contact channel). Most critically, 'confirm_submission' (a boolean gate defaulting to false on a non-idempotent mutating submission) is never mentioned, which could cause the agent to submit without confirming.

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 states a specific verb and resource ('Submit a multi-line electronic component BOM') plus the destination and process ('human sourcing in Shenzhen'), which an agent can act on immediately. It implicitly distinguishes itself from the single-component sibling submit_component_rfq via 'multi-line BOM' and 'one sourcing request for the complete BOM', but never names that sibling, so differentiation is inferred rather than explicit.

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 makes clear what the call produces and that quoting/purchasing is out of scope, which implies usage for batch sourcing inquiries. However, it gives no guidance on when to prefer this over submit_component_rfq or request_huaqiangbei_search, and no prerequisites (e.g. that the user must supply a valid email for follow-up).

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