Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

get_sourcing_capabilities

Read-onlyIdempotent

Describe Jurk's human electronic component sourcing capabilities in Shenzhen, including BOM, hard-to-find, obsolete, EOL and spot-market sourcing. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sourcing_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesYes
serviceYes
locationYes
capabilitiesYes
human_reviewYes
real_time_inventoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The description's only behavioral statement is 'Read-only', which merely restates readOnlyHint=true and adds nothing beyond the annotations. For a static informational endpoint there is little other behavior to disclose, and the output schema carries the return shape, so the gap is modest but real.

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?

One front-loaded sentence covers purpose and scope efficiently. The trailing 'Read-only.' is redundant with the annotations and could be dropped without losing information.

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?

Annotations plus an output schema mean the description needn't explain safety or return values, and the scope list is adequate. What is missing is routing guidance relative to the sibling capability tools, which is the main ambiguity an agent would face here.

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 there is nothing for the description to disambiguate; baseline 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?

States a specific verb and resource ('describe Jurk's human electronic component sourcing capabilities in Shenzhen') and enumerates the covered service lines (BOM, hard-to-find, obsolete, EOL, spot-market), which separates it from sibling capability tools like get_supplier_check_capabilities and get_shenzhen_execution_capabilities. It stops short of explicitly naming those siblings, so differentiation is by topic list rather than by direct contrast.

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 when-to-use or when-not-to-use guidance. With three similarly named '*_capabilities' tools in the sibling list, an agent is left to infer from the topic list alone which one answers a given question.

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