No user-submitted related servers found.
Scored across 4 tools
Each tool has a distinct role: one lookup of yield data, one list/search, and two calculations in opposite directions (trimming a purchased weight vs. scaling up from a recipe amount). The two calculate_ tools do touch the same edible-yield concept, which could cause occasional misselection, but the descriptions make the direction of each clear.
All four tools use a consistent snake_case verb_noun pattern (get_, calculate_, calculate_, list_) with clear object naming. No mixing of conventions or casing styles.
Four tools is well-scoped for a narrow, focused domain (USDA vegetable yield lookup and yield-based calculations). Each tool earns its place with no obvious redundancy.
The surface covers per-item lookup, enumeration/filtering, trim calculation, and purchase-amount calculation, covering the core workflow end to end. Minor gaps exist (e.g. no bulk/multi-item calculations or cooked-yield handling), but agents can work around these with repeated calls.