Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

get_shenzhen_execution_capabilities

Read-onlyIdempotent

Return Vladimir's Shenzhen physical human-execution capabilities. Use this to discover tasks that require a person on the ground. 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_shenzhen_execution_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesYes
serviceYes
locationYes
handled_byYes
capabilitiesYes
human_reviewYes
guarantees_outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read-only" in the description is pure repetition of structured data. Beyond that it discloses nothing about what the capability set contains or its scope. For a zero-parameter lookup with a full annotation set and an output schema the bar is low, so a 3 is fair.

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?

Three short sentences, front-loaded with the resource, then usage, then a safety note. Almost no waste, with the only slack being the redundant "Read-only" sentence.

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?

The tool is a simple, parameterless, read-only lookup with an output schema that describes the returns, so the description needn't explain results. It covers what and when adequately. The one remaining gap is what "capabilities" concretely encompasses, which a sibling comparison would have resolved.

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 no parameters, and the description correctly does not invent any. Its mention of Shenzhen and physical execution is consistent with the zero-argument design. Baseline 4 applies for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return Vladimir's Shenzhen physical human-execution capabilities" restates the tool name almost verbatim, so the core purpose is only loosely specified. The second sentence adds real meaning by framing it as discovery of tasks that require a person on the ground, which is what saves it from tautology. It does not distinguish itself from the adjacent get_shenzhen_execution_contact or shenzhen_errand siblings.

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?

"Use this to discover tasks that require a person on the ground" gives an implied when-to-use condition. There is no explicit when-not, and no mention of the closest alternatives (get_shenzhen_execution_contact, shenzhen_errand, request_on_site_check), so the agent must infer routing.

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