Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

submit_supplier_check

Submit a China supplier or seller for human verification. Can request remote checking or indicate that an on-site Shenzhen visit may be needed. Submission does not certify or guarantee the supplier.

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": {
      "supplier": "<supplier>",
      "request": "<request>",
      "contact": "<contact>"
    },
    "name": "submit_supplier_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
visitNonot_sure
contactYes
requestYes
languageNoen
supplierYes
confirm_submissionNo

Output Schema

NameRequiredDescriptionDefault
messageYes
acceptedYes
locationYes
referenceYes
handled_byYes
on_site_requestedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already state readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description usefully adds that the outcome is 'human verification' and that 'Submission does not certify or guarantee the supplier,' which sets expectations about the result. It does not disclose what confirm_submission does, whether an unconfirmed submission is a no-op, or what the response contains.

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?

Two compact sentences put the core action first and the caveat last; every sentence carries information. However, brevity here comes at the cost of parameter detail rather than from ruthless editing, so it falls short of ideal.

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

Completeness2/5

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

For a 6-parameter mutation tool with 0% schema description coverage, the description is thin. It omits the semantics of confirm_submission and contact, and it does not explain what happens after submission, whether the request is queued, or what the outputs represent. An output schema exists, so return values need not be described, but the invocation-critical gaps remain.

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 6 parameters, but the description clarifies only three loosely: supplier, request ('remote checking'), and visit ('on-site Shenzhen visit'). It says nothing about contact, language, or the critical confirm_submission boolean, which defaults to false and presumably gates the actual submission. That gap matters greatly for correct invocation.

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 gives a specific verb and resource: 'Submit a China supplier or seller for human verification.' This is clearly distinguishable from read-side siblings such as get_supplier_check_capabilities or verify_seller_claim. However, it never explicitly contrasts itself with overlapping siblings such as request_on_site_check or verify_stock_on_site.

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 by noting that the caller may 'request remote checking or indicate that an on-site Shenzhen visit may be needed.' It gives no explicit when-not-to-use and no comparison with request_on_site_check, request_market_price_check, or other verification siblings, so the agent must infer the boundary.

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