Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

get_shenzhen_execution_contact

Read-onlyIdempotent

Return the public service identity for Vladimir's Shenzhen Human Execution and supplier-verification branch. 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_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
roleYes
websiteYes
locationYes
physical_tasks_availableYes
supplier_check_availableYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's "Read-only" sentence simply restates readOnlyHint and adds no new behavioral context such as the scope of the returned identity or whether it is stable over time. Adequate only because the annotations carry the burden.

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, the identifying information is front-loaded, and nothing is padded. The trailing "Read-only." is redundant with the annotations and is the one sentence that does not earn its place.

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?

With an output schema present, return-value explanation is unnecessary, and a zero-parameter tool needs little input guidance, so the core is covered. What is missing is how this identity record relates to the sibling contact and capability tools, leaving the agent to guess at invocation context.

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, which is the baseline-4 case: there is nothing for the description to disambiguate. The empty schema is consistent with the description, which implies a single fixed lookup.

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 uses a concrete verb ("Return") and a specific resource ("public service identity") scoped to one named branch, so the agent knows what it fetches. It does not explicitly distinguish itself from the closely named sibling get_contact, which is the main remaining ambiguity.

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 get_contact, get_shenzhen_execution_capabilities, or get_service_area, all of which plausibly relate to the same branch. The agent must infer the use case from the noun phrase alone.

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