Jurk Shenzhen Electronic Component Sourcing

Get Jurk Contact

get_contact

Read-onlyIdempotent

Return the public Jurk sourcing contact and available request channels. Read-only.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`name`	Yes
`role`	Yes
`website`	Yes
`location`	Yes
`rfq_available`	Yes
`supplier_check_available`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

addedOutput schema / properties / role

Added value: +{
+  "title": "Role",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "website",
-  "location",
-  "rfq_available",
-  "supplier_check_available"
-]New value: +[
+  "name",
+  "role",
+  "website",
+  "location",
+  "rfq_available",
+  "supplier_check_available"
+]

AddedOct 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description is a restatement rather than new information. The only added context is that the contact is 'public' and that request channels are returned, which is modest value on top of the annotation set.

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?

Two short sentences, front-loaded with the purpose and followed by the safety profile. Nothing is wasted or buried.

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?

With an output schema present, the return shape need not be described, and the annotations fully cover the safety profile. The remaining gap is the absence of routing guidance among the many contact/capability siblings.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics for the description to explain.

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 and resource: return the public Jurk sourcing contact plus available request channels. This is distinguishable from the near-neighbor get_shenzhen_execution_contact by naming the Jurk sourcing context, though it does not explicitly contrast with that sibling.

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?

There is no statement of when to call this versus the many sibling contact/capability tools, and no prerequisites or exclusions. 'Read-only' is a property, not usage guidance.

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

All Jurk Shenzhen Electronic Component Sourcing 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?