Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

get_supplier_check_capabilities

Read-onlyIdempotent

Describe independent China supplier checking and optional physical on-site verification capabilities in Shenzhen. 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_supplier_check_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesYes
serviceYes
locationYes
guaranteeYes
capabilitiesYes
on_site_availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the closing "Read-only." sentence is largely restating structured data. The description does add real context by naming the two capability domains it covers (independent supplier checking, optional physical on-site verification) and the Shenzhen constraint, but says nothing about how the capabilities are presented or whether they represent commitments versus informational scope.

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 short sentences, front-loaded with the substantive scope (supplier checking plus on-site verification) before the qualifier. The only wasted element is the trailing "Read-only.", which duplicates the annotations rather than adding information.

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 no parameters, full annotation coverage, and an output schema handling return values, the description only needs to convey what domain of capabilities is described — which it does. It would be stronger if it clarified how this differs from the other capability-listing siblings, but nothing required to invoke it is missing.

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 4 applies. The description correctly implies no inputs are needed to retrieve the capability summary.

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 ("Describe") and a specific scope: independent China supplier checking plus optional physical on-site verification in Shenzhen. It is clearly distinct from action siblings like request_on_site_check or submit_supplier_check, though it never explicitly names the nearby capability siblings (get_sourcing_capabilities, get_shenzhen_execution_capabilities) to sharpen the boundary.

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?

Usage is only implied: an agent can infer this is the discovery call to make before committing to a supplier check or an on-site verification. There is no explicit statement of when to call this versus get_sourcing_capabilities, get_shenzhen_execution_capabilities, or request_on_site_check, and no stated prerequisites.

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