Freightgate

Agent readability score

Strengths

• Tool names generally align with their purposes (e.g., 'shippingrates_dd_calculate' for D&D cost breakdowns).
• Descriptions include usage scenarios (e.g., 'use this for carrier selection').

Weaknesses

• Multiple descriptions are truncated mid-sentence (e.g., 'shippingrates_stats' cuts off mid-explanation).
• Parameter schemas and input requirements are not explicitly defined in any tool's description.
• Some tools have overlapping purposes (e.g., 'shippingrates_inland_haulage' vs. 'shippingrates_inland_compare').

• shippingrates_stats — Description abruptly cuts off mid-sentence without completion
• shippingrates_lines — Unclear if 'per-country record counts' are optional or required parameters
• shippingrates_total_cost — No explicit mention of required input parameters like FX rates or container type
• shippingrates_congestion — No explanation of how to handle null values in congestion measurements
• shippingrates_inland_compare — Ambiguous if 'port-to-ICD/city pair' is a required input parameter

Verdict

The toolset provides clear functional intent but suffers from incomplete documentation and parameter ambiguity. Truncated descriptions and missing input schema details risk misinterpretation by agents, while overlapping tool purposes create potential selection conflicts.

9/11/2026, 4:06:44 AM

Event narrative

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

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from null to 'auth-gated', complianceScore remained null · Agent moved to a new security model but compliance metrics were not yet available
• 2026-09-11T03:50:39.090Z — era changed from 'auth-gated' to 'legacy', complianceScore increased from null to 100 · Agent stabilized in legacy mode with full compliance achieved

Advice

Monitor complianceScore trends for stability. Check smokeOk status as it remains null despite era change. Verify if legacy mode requirements are fully met.