GST Cranes Public Discovery MCP

Agent readability score

Strengths

• Tools are focused on distinct public data categories (resources, wanted ads, wiki records).
• Descriptions explicitly state the scope of each tool's output.

Weaknesses

• Tool names are generic and could be more specific (e.g., 'list_public_resources' is too broad).
• No explicit parameter definitions or constraints in tool descriptions.
• Potential overlap between 'list_public_resources' and 'list_wanted_ads' (both mention marketplace data).

• list_public_resources — Vague scope (marketplace, wanted ads, etc.) may cause confusion with other tools
• list_wanted_ads — No clarification on filtering parameters for buyer-specific queries
• list_crane_wiki_records — Unclear how to specify record types (company, fleet, country, etc.)

Verdict

Tools provide clear functional separation but lack parameter specificity and have minor overlap. The read-only focus aligns with the server's public access mandate, but improved schema documentation would enhance usability.

9/11/2026, 8:16:44 AM

Event narrative

Server transitioned from auth-gated to legacy era with compliance score set to 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · indicates shift to legacy system with potential reduced security controls
• 2026-09-11T07:35:54.413Z — complianceScore changed from null to 100 · shows full compliance achieved after era transition

Advice

Monitor compliance score stability. Verify legacy era configuration aligns with security policies. Check for smokeOk updates in future measurements.