Skip to main content
Glama

Jurk Shenzhen Electronic Component Sourcing

get_recent_cases

Read-onlyIdempotent

Return public recent sourcing cases when verified case data is available. The tool never invents customer cases. 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_recent_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
casesYes
notesYes
availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the trailing 'Read-only.' sentence is largely redundant. The genuinely additive content is 'The tool never invents customer cases', which discloses a data-authenticity guarantee not expressible in annotations. It still omits what 'recent' means and what an empty result looks like.

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 core action and resource. The final 'Read-only.' sentence earns little place given the readOnlyHint annotation already says it, which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and an output schema present, the description only needs to convey what the tool returns and any behavioral caveats, and it does both: public recent sourcing cases plus a no-fabrication guarantee. The one soft spot, the undefined 'recent' window, is a minor detail the output schema likely resolves.

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 no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 public recent sourcing cases'. The scope qualifier 'public' and 'recent' narrows it meaningfully, and the resource is distinct from sibling tools like get_sourcing_capabilities or verify_seller_claim. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

The phrase 'when verified case data is available' hints at a precondition and implies the tool may return nothing, which is useful. However, it never says when an agent should reach for this tool versus the many sibling capabilities tools, nor does it give any exclusion criteria. Usage is implied rather than directed.

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